[WireGuard] [PATCH 3/4] Explain the optional nature of Peer.EndPoint more clearly

Jason A. Donenfeld Jason at zx2c4.com
Fri Jul 1 04:08:08 CEST 2016

I'm merging a commit with some of these suggested changes for 1,2,4.
Thanks for those. But the changes here are simply not correct.

The endpoint is simply the initial endpoint used to contact the peer.
If the peer sends legit traffic from a different endpoint, it will be
updated to that new endpoint. So, specifying an endpoint doesn't bind
traffic to that endpoint. It's simply an initial specifier of it.
Otherwise, how does traffic get started flowing?

More information about the WireGuard mailing list