Date: Wed, 24 Jul 2024 14:48:53 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 280390] NPTv6 not working Message-ID: <bug-280390-7501-Wv0tBxjURK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280390-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-280390-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280390 --- Comment #14 from John Hay <john@sanren.ac.za> --- Looking at your tcpdumps, one can see that the packets are correctly transl= ated before being transmitted, so that part is working. The problem is that beca= use the vtnet0 interface is an ethernet like interface, the kernel is only goin= g to accept or respond to the addresses that are configured on the interface. Th= at is why you see the router sending neighbor solicitation messages, but your = vm does not respond to them. That is not a ipfw or nptv6 problem, but more a kernel networking thing. If you can get another /64 from vultr that they will route to you, you can configure that on lo0 and then let nptv6 use that for the external prefix. Where I have seen nptv6 work with a /64 ipv6 address that is configured on = the external interface is with pppoe setups, but ppp and tun interfaces behave differently, they do not need neighbor solicitations, packets are just sent. If you only have a few devices, you might be able to configure proxy ndp for their external addresses, but I have not tried that. --=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-280390-7501-Wv0tBxjURK>