From: Silvan Nagl <mail@53c70r.de>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: wg-quick up automation fails
Date: Sun, 2 Jun 2019 01:49:21 +0200 [thread overview]
Message-ID: <b46b6815-347b-1410-51df-db52c7386313@53c70r.de> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1323 bytes --]
G'day,
i recently upgrade WireGuard to the latest shipped Debian version
(0.0.20190406-1) and noticed my wg-quick created interface did not come
up as usual anymore. (Also tried the git master branch) I tried to
single command trough wg-quick's automation to reproduce the error;
automatic:
[#] ip link add Y type wireguard
[#] wg setconf Y /dev/fd/63
[#] ip address add X.X.X.X/32 dev Y
[#] ip address add fc00::XXXX/128 dev Y
[#] ip link set mtu XXXX up dev Y
[#] resolvconf -a tun.Y -m 0 -x
[#] wg set Y fwmark 51820
[#] ip -6 route add ::/0 dev Y table 51820
RTNETLINK answers: No such device
[#] resolvconf -d tun.Y
[#] ip link delete dev Y
manual:
> ip link add Y type wireguard
> wg setconf Y <(wg-quick strip /etc/wireguard/Y.conf)
> ip address add X.X.X.X/32 dev Y
> ip address add fc00::XXXX/128 dev Y
> ip link set mtu 1268 up dev Y
> resolvconf -a tun.X -m 0 -x
> wg set Y fwmark 51820
> ip -6 route add ::/0 dev Y table 51820
< RTNETLINK answers: No such device
(MTU may be to low here so i set it higher again)
> ip link set mtu 1420 up dev Y
> ip -6 route add ::/0 dev Y table 51820 (works now)
breaks up @ this point because of error handling...
Additionally it could be possible the MTU isn't set correctly.
Greetings,
53c70r
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-06-01 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 23:49 Silvan Nagl [this message]
2019-06-02 6:32 ` XRP
2019-06-02 10:27 ` Silvan Nagl
2019-06-02 10:38 ` Silvan Nagl
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=b46b6815-347b-1410-51df-db52c7386313@53c70r.de \
--to=mail@53c70r.de \
--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).