Date: Sat, 13 Feb 2021 19:13:21 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 253488] wg(4) IPv6 endpoints not supported yet Message-ID: <bug-253488-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253488 Bug ID: 253488 Summary: wg(4) IPv6 endpoints not supported yet Product: Base System Version: 13.0-STABLE Hardware: amd64 OS: Any Status: New Keywords: ipv6 Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: zarychtam@plan-b.pwste.edu.pl I have asked on D26137 review, then on the freebsd-net@ mailing list but haven't received any useful feedback on this matter, though the code sugges= ts IPv6 endpoints are implemented.=20 When IPv6 endpoint is specified in the form: [IP:v6::address]:port while creating the tunnel from the command line we get only the error: wg0: wg_peer_add bad length for endpoint 28=20 So I modified code in sys/dev/if_wg/module/module.c[1] around line 590 to s= kip this check but compare the lengths. It came out that after this change Wireguard protocol is able to do a handshake with IPv6 specified endpoint, = but sizeof(*endpoint)[1] seems to be always 16(for both legacy IP and IPv6 specified endpoints), what is fine for legacy IP, while for IPv6 endpoint s= ize is 28. After disabling this check no more than Wireguard handshake over IPv6 can be observed. The tunnel is either not created or not able to carry the data.[2] [1] https://cgit.freebsd.org/src/tree/sys/dev/if_wg/module/module.c?id=3D5aaea4= b#n590 [2] https://lists.freebsd.org/pipermail/freebsd-net/2021-February/057463.ht= ml --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253488-227>