[WireGuard] Client changes endpoint port, why?

Jason A. Donenfeld Jason at zx2c4.com
Thu Jul 7 18:38:45 CEST 2016

On Thu, Jul 7, 2016 at 5:00 PM, Bruno Wolff III <bruno at wolff.to> wrote:
> On Thu, Jul 07, 2016 at 14:45:22 +0000,
>  Jan De Landtsheer <jan at incubaid.com> wrote:
>> nope, Start with basics, use pub ip to pub ip
>> BTW, can a client run behind NAT ? (I assume not, as AFAICT both need to
>> listen on a port)
> The one behind nat can hold the tunnel open so the other end can always
> reach it.

This is the thrust of the issue -- holding the tunnel open when
there's no traffic. This needs to be addressed. Started new thread to
discuss this.

More information about the WireGuard mailing list