From: XRP <xrp@airmail.cc>
To: wireguard@lists.zx2c4.com
Subject: Wireguard fails to start when adding IPv6 to AllowedIP
Date: Sun, 03 Mar 2019 08:56:12 +0100 [thread overview]
Message-ID: <196a105a94a39c3a2e23338880d647f5825dd97a.camel@airmail.cc> (raw)
Wireguard fails to start when adding an IPv6 to AllowedIP.
Example Config:
[Interface]
PrivateKey = 0OpsgK/Wl7VJC2I49UiGL91wBlbqN+XP0R+bSH+VL2w=
MTU = 1200
Address = 10.0.0.5/24,fdb8:a70c:b109:9935::1/64
[Peer]
PublicKey = hk7hdCE2vKFu895RiCYhQTK6V9+zhnI+KI46VVSx1DA=
AllowedIPs = 10.0.0.1/24,fdb8:a70c:b109:9935::/64
Endpoint = 127.0.0.1:50300
Here's what happens when I try to start the config with wg-quick:
# wg-quick up wg1
[#] ip link add wg1 type wireguard
[#] wg setconf wg1 /dev/fd/63
[#] ip address add 10.0.0.5/24 dev wg1
[#] ip address add fdb8:a70c:b109:9935::1/64 dev wg1
[#] ip link set mtu 1200 up dev wg1
[#] ip route add fdb8:a70c:b109:9935::/64 dev wg1
RTNETLINK answers: No such device
[#] ip link delete dev wg1
I could reproduce this behaviour under ArchLinux and OpenSuse.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-03-20 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 7:56 XRP [this message]
2019-03-20 22:36 ` Wireguard fails to start when adding IPv6 to AllowedIP Roman Mamedov
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=196a105a94a39c3a2e23338880d647f5825dd97a.camel@airmail.cc \
--to=xrp@airmail.cc \
--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).