Re: Another roaming problem

["Toke Høiland-Jørgensen" <toke@toke.dk>]

On 8 March 2018 17:18:47 CET, "Jason A=2E Donenfeld" <Jason@zx2c4=2Ecom> w=
rote:
>Hi Toke,
>
>On Thu, Mar 8, 2018 at 3:29 PM, Toke H=C3=B8iland-J=C3=B8rgensen <toke@to=
ke=2Edk>
>wrote:
>> So is there a way to either tell the client not to change its idea of
>> the endpoint, or to tell the server to always use a certain source
>> address for outgoing packets?
>
>There have been some discussions on adding another [gasp] nob to clamp
>an endpoint, for this reason and some other related ones=2E But the
>source address caching is supposed to be sticky=2E That is -- it's
>supposed to be that WireGuard will use the correct source address
>based on in the prior incoming packet=2E I can try to reproduce to see
>if perhaps you're uncovering some incorrect behavior here=2E More
>generally speaking, it seems like this problem is occurring for you
>because of NAT=20

Well, in the sense that this wouldn't be a problem if there was no NAT on =
the internet, sure=2E=2E=2E

But other than that, how is it related to NAT?

> and so I wonder if a simpler solution would also
>involve NAT -- namely, configuring "hair pin" NAT?

What's that?

-Toke