Development discussion of WireGuard
 help / color / mirror / Atom feed
From: lejeczek <>
Subject: firewall / port forward - ?
Date: Wed, 16 Feb 2022 14:43:23 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi guys.

I'm still new to wireguard and still not an expert on network stack so I 
struggle with something what might be trivial.

A roadwarrior when connected to the server sees a forward-port on 
server's internal network as 'closed': -> <server> (port forward) => (a 
dummy iface, still server)

but rest of sees that forwarded port - as I expected - as 'open'

If that same server port is not forwarded ("stays" on then 
that roadwarrior sees the port as 'open'

I've fiddled with firewall all I could so I think it's not in there - 
thus hoping expert(s) can help me wrap my head around it.

many thanks, L.

           reply	other threads:[~2022-02-16 14:43 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: firewall / port forward - ?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).