Roaming Mischief

Markus Woschank markus.woschank at
Fri Nov 17 18:23:20 CET 2017

> WireGuard is not a client-server architecture
Did not claim otherwise.

> by removing the endpoint, you are preventing this peer from initiating.

Two peers forming a connection have the following properties/aspects:
* at least one has a fixed IP/DNS entry and this is set in the
configuration as endpoint in the other peer's configuration
* if one peer is in roaming mode it makes no sense to specify it's
endpoint in the other peers's configuration
* if both peers have fixed addresses it makes sense to specify each
other endpoint IPs in the configuration so the connection can be
established from both sides at any time

Please prove me wrong and supply an example where it makes sense to
have a roaming peer's endpoint set, where the roaming peer _really_
roams (changes it's IP) and where on reboot/reset/whatsoever the
originally set endpoint IP in the configuration magically makes any
sense again.


More information about the WireGuard mailing list