From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Baptiste Jonglez <baptiste@bitsofnetworks.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Multiple Endpoints
Date: Mon, 9 Jan 2017 00:00:17 +0100 [thread overview]
Message-ID: <CAHmME9pSJ3gsAUdNhk_Lt-QzOf6+eS=cay_Chq8YpdcaZJbCsA@mail.gmail.com> (raw)
In-Reply-To: <20170108225732.GC9445@tuxmachine.polynome.dn42>
On Sun, Jan 8, 2017 at 11:57 PM, Baptiste Jonglez
<baptiste@bitsofnetworks.org> wrote:
> Please read Emmanuel's email more carefuly before being so assertive.
> His use-case was a client behind a stateful firewall, so if the server
> changes its IP address, roaming will not work.
I understand that use-case. And as I said before, most UDP stateful
firewalls allow changing remote IPs, so long as the dport/sport remain
the same.
> I merely pointed out that a stateful firewall is similar to a symmetric
> NAT, that is, both would cause issue with peer roaming.
Are you sure about this for UDP? I did a bunch of tests several months
ago, and was able to punch holes in a variety of stateful firewalls
with changing remote IPs.
next prev parent reply other threads:[~2017-01-08 22:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 14:43 em12345
2017-01-07 15:23 ` Jason A. Donenfeld
2017-01-07 16:45 ` em12345
2017-01-08 14:12 ` Baptiste Jonglez
2017-01-08 14:39 ` Jörg Thalheim
2017-01-08 21:22 ` Baptiste Jonglez
2017-01-08 22:19 ` Jason A. Donenfeld
2017-01-08 22:18 ` Jason A. Donenfeld
2017-01-08 22:57 ` Baptiste Jonglez
2017-01-08 23:00 ` Jason A. Donenfeld [this message]
2017-01-09 11:35 ` Varying source address and stateful firewalls (Was: Multiple Endpoints) Baptiste Jonglez
2017-01-10 4:32 ` Jason A. Donenfeld
2017-01-15 10:01 ` Multiple Endpoints Jason A. Donenfeld
2017-01-08 22:14 ` Jason A. Donenfeld
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='CAHmME9pSJ3gsAUdNhk_Lt-QzOf6+eS=cay_Chq8YpdcaZJbCsA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=baptiste@bitsofnetworks.org \
--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).