From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: markus.woschank@gmail.com Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 0b930602 for ; Fri, 17 Nov 2017 18:34:24 +0000 (UTC) Received: from mail-ot0-f181.google.com (mail-ot0-f181.google.com [74.125.82.181]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 7a8bb5dd for ; Fri, 17 Nov 2017 18:34:24 +0000 (UTC) Received: by mail-ot0-f181.google.com with SMTP id s4so2796527ote.4 for ; Fri, 17 Nov 2017 10:38:55 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <593d6d3a-550e-a14d-4c1d-f7ee8e731d87@gmail.com> From: Markus Woschank Date: Fri, 17 Nov 2017 19:38:54 +0100 Message-ID: Subject: Re: Roaming Mischief To: Aaron Jones Content-Type: text/plain; charset="UTF-8" Cc: WireGuard mailing list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > 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. Markus