wg-quick systemd service does not work directly after boot

Matthias Urlichs matthias at urlichs.de
Wed Feb 7 14:06:46 CET 2018

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

More information about the WireGuard mailing list