From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Another roaming problem
Date: Thu, 8 Mar 2018 18:02:38 +0100 [thread overview]
Message-ID: <CAHmME9p0aW2i-EcErua_Hkz-hZc12m47oLR9wvngu5ejVX=Q8A@mail.gmail.com> (raw)
In-Reply-To: <85FE1433-439D-439C-A61E-B17754707077@toke.dk>
On Thu, Mar 8, 2018 at 5:59 PM, Toke H=C3=B8iland-J=C3=B8rgensen <toke@toke=
.dk> wrote:
>> and so I wonder if a simpler solution would also
>>involve NAT -- namely, configuring "hair pin" NAT?
>
> What's that?
It's the terrible vendor term for hitting the gateway through one of
its IPs (say, the public one) and having it forward packets for you to
another machine on the same LAN. The idea here, being, you'd get to
keep using the same IP address for communicating, even when you're
behind NAT in the private network. (This seems to work well for me at
my house.)
Wikipedia describes it in terms of the p2p discovery issue, which is
slightly different, but still the same underlying concept:
https://en.wikipedia.org/wiki/Hairpinning
next prev parent reply other threads:[~2018-03-08 16:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 14:29 Toke Høiland-Jørgensen
2018-03-08 14:49 ` Matthias Urlichs
2018-03-08 16:18 ` Jason A. Donenfeld
2018-03-08 16:59 ` Toke Høiland-Jørgensen
2018-03-08 17:02 ` Jason A. Donenfeld [this message]
2018-03-08 17:23 ` Toke Høiland-Jørgensen
2018-03-08 17:39 ` Jason A. Donenfeld
2018-03-08 17:50 ` Toke Høiland-Jørgensen
2018-03-08 18:03 ` Jason A. Donenfeld
2018-03-09 10:08 ` Toke Høiland-Jørgensen
2018-03-09 14:32 ` Toke Høiland-Jørgensen
2018-03-09 14:35 ` Jason A. Donenfeld
2018-03-09 14:42 ` Toke Høiland-Jørgensen
2018-03-09 14:39 ` Toke Høiland-Jørgensen
2018-03-09 14:41 ` Jason A. Donenfeld
2018-03-09 14:46 ` Toke Høiland-Jørgensen
2018-03-09 14:48 ` Jason A. Donenfeld
2018-03-09 14:53 ` Toke Høiland-Jørgensen
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='CAHmME9p0aW2i-EcErua_Hkz-hZc12m47oLR9wvngu5ejVX=Q8A@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=toke@toke.dk \
--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).