From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Adrián Mihálko" <adriankoooo@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard behind NAT
Date: Sat, 14 Apr 2018 04:06:11 +0200 [thread overview]
Message-ID: <CAHmME9pYzb8M8379twgRNVU2gsZOWuwvBuBe2G1rorvekVzX_w@mail.gmail.com> (raw)
In-Reply-To: <CA+Hw3eZewB594vvxXOgYLKgZRGT-CNPHJvtgfgXQhH_Bj-ussg@mail.gmail.com>
If you can have SIDE_A connect to SIDE_B and enable
persistent-keepalive, that should take care of things mostly. If you
can't do that for whatever reason, there are hole punching tricks like
[1] and [2].
[1] https://git.zx2c4.com/WireGuard/tree/contrib/examples/nat-hole-punching
[2] https://github.com/manuels/wireguard-p2p
next prev parent reply other threads:[~2018-04-14 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 11:22 Wireguard behind NAT Adrián Mihálko
2018-04-14 2:06 ` Jason A. Donenfeld [this message]
2018-09-02 19:51 Adrián Mihálko
2018-09-07 3:39 ` Jason A. Donenfeld
2018-09-07 15:17 ` Steven Honson
2018-09-03 10:28 Adrián Mihálko
2018-09-03 10:43 ` Ole-Morten Duesund
2018-09-03 10:55 ` Roman Mamedov
2018-09-03 10:59 ` Ole-Morten Duesund
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=CAHmME9pYzb8M8379twgRNVU2gsZOWuwvBuBe2G1rorvekVzX_w@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=adriankoooo@gmail.com \
--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).