GNU bug report logs - #53381
wireguard service can fail on boot by starting before DNS is ready

Previous Next

Package: guix;

Reported by: Nathan Dehnel <ncdehnel <at> gmail.com>

Date: Thu, 20 Jan 2022 03:44:01 UTC

Severity: normal

To reply to this bug, email your comments to 53381 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guix <at> gnu.org:
bug#53381; Package guix. (Thu, 20 Jan 2022 03:44:01 GMT) Full text and rfc822 format available.
Acknowledgement sent to Nathan Dehnel <ncdehnel <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Thu, 20 Jan 2022 03:44:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Nathan Dehnel <ncdehnel <at> gmail.com>
To: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix <at> gnu.org>
Subject: wireguard service can fail on boot by starting before DNS is ready
Date: Wed, 19 Jan 2022 21:42:54 -0600

As shown here on boot:

[#] ip link add test type wireguard
[#] wg setconf test /dev/fd/63
Name or service not known: `<other server FQDN>:51820'
Configuration parsing error
[#] ip link delete dev test
failed to start service 'wireguard-test'

This can cause remote machines to become inaccessible.

Is there an equivalent of systemd-networkd-wait-online.service? Or
perhaps you would accept a patch to enable the "respawn?" service
method, so wireguard will eventually connect once DNS is ready?
This bug report was last modified 2 years and 97 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.