Re: new in-kernel wireguard and IPv6 endpoint

May be. I have nothing to suggest, sorry. I never used IPv6 in real life. чт, 4 февр. 2021 г., 10:44 Marek Zarychta : > W dniu 04.02.2021 o 05:25, Vasily Postnicov pisze: > > If the endpoint does not use the same WireGuard implementation from > FreeBSD, try to cherry-pick this commit first and th

Re: new in-kernel wireguard and IPv6 endpoint

W dniu 04.02.2021 o 05:25, Vasily Postnicov pisze: If the endpoint does not use the same WireGuard implementation from FreeBSD, try to cherry-pick this commit first and then rebuild and reinstall the kernel. https://cgit.freebsd.org/src/commit/?id=5aaea4b99e5cc724e97e24a68876e8768d3d8012

Re: new in-kernel wireguard and IPv6 endpoint

If the endpoint does not use the same WireGuard implementation from FreeBSD, try to cherry-pick this commit first and then rebuild and reinstall the kernel. https://cgit.freebsd.org/src/commit/?id=5aaea4b99e5cc724e97e24a68876e8768d3d8012 ср, 3 февр. 2021 г., 23:13 Marek Zarychta : > W dniu 21.01

Re: new in-kernel wireguard and IPv6 endpoint

W dniu 21.01.2021 o 20:03, Marek Zarychta pisze: Dear subscribers, please let me know if is it possible to use IPv6 addressed endpoint for the tunnel? I have tried to specify the address enclosed in [] followed by the port number, for example: [2001:db8:0:1::1]:54333, have tried without it: 2

new in-kernel wireguard and IPv6 endpoint

Dear subscribers, please let me know if is it possible to use IPv6 addressed endpoint for the tunnel? I have tried to specify the address enclosed in [] followed by the port number, for example: [2001:db8:0:1::1]:54333, have tried without it: 2001:db8:0:1::1:54333. I have also tried to specify