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 eb4cad25 for ; Sat, 18 Nov 2017 15:07:18 +0000 (UTC) Received: from mail-oi0-f43.google.com (mail-oi0-f43.google.com [209.85.218.43]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 714589eb for ; Sat, 18 Nov 2017 15:07:18 +0000 (UTC) Received: by mail-oi0-f43.google.com with SMTP id a75so3581956oib.1 for ; Sat, 18 Nov 2017 07:11:55 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <593d6d3a-550e-a14d-4c1d-f7ee8e731d87@gmail.com> From: Markus Woschank Date: Sat, 18 Nov 2017 16:11:54 +0100 Message-ID: Subject: Re: Roaming Mischief To: WireGuard mailing list Content-Type: text/plain; charset="UTF-8" List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sorry for the previous message. @matthias > Simple example: a mobile IP phone. Rebooting your telephony server > causes you to drop the connection to the client until _it_ next issues a > call. However, if you persist the phone's address, you don't lose > incoming service. Thank you for the example. While a reboot already impacts the service of the telephony system this might be also tackled via the persistent keepalive, but I see your point. But then again the original configuration did not specify any endpoint and suddenly, after reboot, it does. I strongly believe the state (current endpoint of roaming peers) needs to be separated from the configuration. Take the dhcpd server for example, it does _not_ store leases in the configuration and rewrites it on every shutdown, it stores the _state_ at a different location. Again ;) my proposal: if a peer's endpoint is specified this makes it a non roaming peer, make it possible to store and restore, and/or set current roaming peers endpoints, for special situations and don't change the configuration syntax. Markus