On 8/27/20 7:07 AM, Simon Fryer wrote: > All, > > On Thu, 27 Aug 2020 at 08:17, Alarig Le Lay <ala...@swordarmor.fr> wrote: > >> Hi, >> >> On Tue 25 Aug 2020 15:27:27 GMT, Aisha Tammy wrote: >>> (peer A)$ tcpdump -inet6 -i vio0 icmp6 >>> 15:23:04.918459 fe80::fc00:2ff:feee:5248 > ff02::1:ff42:6: icmp6: >>> neighbor sol: who has 2001:19f0:5:5cd5::6942:6 >>> >>> (a lot of such lines) >> >> It seems that you have been provided a *connected* /64, so the router >> tried to do NDP for your peer, which isn’t possible because the peer >> isn’t on the same L2. >> >> You have ask your provider to *route* you a range. Then, it will be your >> VM that will manage it. >> > > Thank you very much. I have been struggling with exactly the same problem > but with an Iked created IPSec tunnel. Off to raise a query with my > provider. > > Thanks again. > > Simon. >
I found this out too when talking with ncon@ on irc. He has sent a patch which should allow us to use ndp with wg, am not sure if ndp works with (or is even designed to work with) ipsec ipv6. My knowledge of network layers is on demand wikipedia/google, which I assume is also most people attempting to set up tunnels XD So these behaviours put me in a twist. Should get solved soon though. Aisha.
