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
