From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: jugs@protonmail.ch Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id d39d5349 for ; Thu, 8 Feb 2018 19:08:20 +0000 (UTC) Received: from mail3.protonmail.ch (mail3.protonmail.ch [185.70.40.25]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id edaed875 for ; Thu, 8 Feb 2018 19:08:20 +0000 (UTC) Date: Thu, 08 Feb 2018 14:14:18 -0500 From: jugs Cc: "wireguard@lists.zx2c4.com" Subject: Re: wg-quick systemd service does not work directly after boot Message-ID: <5KOTFDe17sagyWs3-jk_vBjCoyO5MvpXPA5Dyp6wjGl8EuDcki0nfOUxFbFpM4aPzeI93mpIdHaACKCUdB3CGQ==@protonmail.ch> In-Reply-To: <3e901b97-c67f-728b-332b-b301bb466dba@urlichs.de> References: <3e901b97-c67f-728b-332b-b301bb466dba@urlichs.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Reply-To: jugs List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Or just use the IP address in the config? =E2=80=8B-jugs =E2=80=8B -------- Original Message -------- On February 7, 2018 1:06 PM, Matthias Urlichs wrote: >On 07.02.2018 12:54, Mytril wrote: >>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. >> >Right. There cannot be a "correct" way of ordering wireguard vs. other > interfaces that works in all circumstances. > > However, instead of sleeping, a dependency on network-online.target > might be more appropriate if wireguard needs to resolve a name. > > >-- Matthias Urlichs > > >WireGuard mailing list >WireGuard@lists.zx2c4.com >https://lists.zx2c4.com/mailman/listinfo/wireguard >