Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Hendrik Friedel" <hendrik@friedels.name>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: Wireguard and double NAT
Date: Fri, 04 Mar 2022 12:03:05 +0000	[thread overview]
Message-ID: <embc5c04ac-b215-462e-b047-6bf76ae1d6ce@envy> (raw)

Hello,

I have a running Server serving several Clients with a wireguard tunnel 
already. For this, port 51820 UDP is porwarded in my router to the 
Server.

Now, I have one Client with a bit of a tricky setup: I have two Routers 
doing NAT. For one of those, I have no control, i.e. I cannot setup 
portforwarding.

Is it still possible, to use Wireguard to create a tunnel between my 
server and this tricky client? If so, is there anything special, that I 
need to consider?

Best regards,
Hendrik


             reply	other threads:[~2022-03-14 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 12:03 Hendrik Friedel [this message]
2022-03-14 22:17 ` Ashish SHUKLA

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=embc5c04ac-b215-462e-b047-6bf76ae1d6ce@envy \
    --to=hendrik@friedels.name \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).