From: Ashish SHUKLA <ashish.is@lostca.se>
To: Hendrik Friedel <hendrik@friedels.name>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard and double NAT
Date: Mon, 14 Mar 2022 22:17:16 +0000 [thread overview]
Message-ID: <20220314221716.h6sfkapawd64ijv6@chateau.d.if> (raw)
In-Reply-To: <embc5c04ac-b215-462e-b047-6bf76ae1d6ce@envy>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
On Fri, Mar 04, 2022 at 12:03:05PM +0000, Hendrik Friedel wrote:
> 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?
IIUC, it's quite possible as long as none of the routers are filtering packets
with following constraints:
- client has to initiate the connection
To increase the reliability of the connectivity:
- preferably not use a fixed listen port in the client, esp. if it's roaming,
or you failover between gateways
- setup PersistentKeepalive
I have a similar setup with my internet connection (behind double NAT), and
it works fine.
HTH
--
Ashish | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0
"Should I kill myself, or have a cup of coffee?" (Albert Camus)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
prev parent reply other threads:[~2022-03-14 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 12:03 Hendrik Friedel
2022-03-14 22:17 ` Ashish SHUKLA [this message]
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=20220314221716.h6sfkapawd64ijv6@chateau.d.if \
--to=ashish.is@lostca.se \
--cc=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).