From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: aranea@aixah.de Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 511c9bd0 for ; Sat, 4 Nov 2017 20:24:11 +0000 (UTC) Received: from wp260.webpack.hosteurope.de (wp260.webpack.hosteurope.de [80.237.133.29]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id d65aeee6 for ; Sat, 4 Nov 2017 20:24:11 +0000 (UTC) Date: Sat, 4 Nov 2017 21:27:01 +0100 From: Luis Ressel To: wireguard@lists.zx2c4.com, Markus Woschank Subject: Re: wg showconf Message-ID: <20171104212701.527fadc1@vega.skynet.aixah.de> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, 4 Nov 2017 21:04:22 +0100 Markus Woschank wrote: > Is there a specific reason for this behaviour? If not, then I would > argue that showconf should reflect the settings used to configure the > interface and not the current state. Peer endpoints are the only part of the information displayed by wg showconf which change dynamically. Wireguard doesn't cache the original endpoint specified by the config (if any), so it's not possible to display it. > Having the output of showconf reflect the original configuration in a > deterministic way enables configuration/provisioning software to check > if the interface is in the desired state and only take action if it's > not - that would be very helpful at least to me. I'd suggest you set up your provisioning software to ignore the endpoints in "wg showconf"'s output if(f) the configuration file doesn't specify endpoints at all. If the config file does contain an endpoint, it's probably a good idea to compare it to the endpoint reported by wg showconf. Cheers, Luis Ressel