From: Erik Jerde <erik@jerde.org>
To: wireguard@lists.zx2c4.com
Subject: Tunnels not coming up on reboot
Date: Thu, 18 Apr 2019 21:07:37 -0500 [thread overview]
Message-ID: <7F8E9113-9721-4AEC-984E-7291AEA9F75D@jerde.org> (raw)
I’ve got two VMs running Ubuntu 18.10 with wireguard 0.0.20190406-wg1~cosmic installed. I’ve enabled the Wireguard interface to come up with the systemctl enable wg-quick@wg0.service on both systems. The interface goes up and down as expected when using the systemctl start and stop commands. My problem is that when either of the VMs are rebooted the tunnels do not come back up. The WG command shows that the interface is up but there’s no handshake/transfer/etc. On the system that was rebooted if I issue a systemctl stop then start command the tunnel comes right up and performs as expected.
I’m pretty green with systemctl but this reminds me of problems I’ve seen with other daemons that didn’t have all of their needs being met before they started. In the old days of init.d I could fix this but now I’m kinda stuck. My .service file is showing After=network-online.target nss-lookup.target and Wants=network-online.target nss-lookup.target. Is there something more that should be in there? Any ideas of what else might be causing the tunnel to not come up?
Thanks!
Erik
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-05-06 20:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7F8E9113-9721-4AEC-984E-7291AEA9F75D@jerde.org \
--to=erik@jerde.org \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).