From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: mytril43@posteo.de Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 51116203 for ; Wed, 7 Feb 2018 11:49:49 +0000 (UTC) Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 8e769831 for ; Wed, 7 Feb 2018 11:49:49 +0000 (UTC) Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 6A5602104F for ; Wed, 7 Feb 2018 12:55:46 +0100 (CET) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3zc0C561LTz9rxD for ; Wed, 7 Feb 2018 12:55:45 +0100 (CET) To: wireguard@lists.zx2c4.com From: Mytril Subject: Re: wg-quick systemd service does not work directly after boot Message-ID: Date: Wed, 7 Feb 2018 12:54:41 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, i have the same problem with the normal way over debian interface. The interface cannot resolve the dynamic domain, because the internet connection is not established at this moment. But i have also only a workaround to create wg0. I also start the wg at a later time. So i think this is not a bug, but rather a problem with the order of network connection startup.