wireguard service can fail on boot by starting before DNS is ready

  • Open
  • quality assurance status badge
Details
One participant
  • Nathan Dehnel
Owner
unassigned
Submitted by
Nathan Dehnel
Severity
normal
N
N
Nathan Dehnel wrote on 20 Jan 2022 04:42
(name . Tobias Geerinckx-Rice via Bug reports for GNU Guix)(address . bug-guix@gnu.org)
CAEEhgEtF_6KO7Xym6TSpF-s0-KTVh_4JLkPX9_311cBDOBdS7Q@mail.gmail.com
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?
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 53381@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 53381
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch