markus.woschank at gmail.com
Fri Nov 17 19:38:54 CET 2017
> Roaming means that the current endpoint (at shutdown time) would be
> persisted, and if the reboot doesn't take very long, it is highly
> likely that the (new) endpoint does still make sense, particularly
> because UDP is used which means new sessions can usually resume as if
> nothing happened, even through a NAT (though if you are also behind a
> NAT, source port randomisation may trip you up if you don't have it
> forwarded through the remote one, but that's beside the point).
Thanks for the example, did not yet have look at wg-quick.
But I argue that the concept of configuration and state should not be mixed.
Having the configuration the same and saving the current state, not
via showconf which should be used for configuration and not state as
the name implies, to a different location and restoring that state
(the current endpoint of the roaming peers) would be much cleaner and
not mix up a state-store-operation that stores a so called
configuration mixed with state that includes the private key.
More information about the WireGuard