Date: Mon, 4 Jan 2021 18:25:05 +0100 From: "Lutz Donnerhacke" <lutz@donnerhacke.de> To: <freebsd-net@freebsd.org> Subject: AW: FreeBSD does not reply to IPv6 Neighbor Solicitations Message-ID: <007601d6e2be$8acf3fb0$a06dbf10$@donnerhacke.de> In-Reply-To: <C3AB2C0C-083C-425A-B4E9-75109ECDE089@lists.zabbadoz.net> References: <006901d6e2a4$4d9d80d0$e8d88270$@donnerhacke.de> <C3AB2C0C-083C-425A-B4E9-75109ECDE089@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> I=E2=80=99d start by checking netstat -s -p icmp6 and netstat -s -p = ip6 for > any suspicious counter updates. Great idea. It points me tot he most stupid error I could make. Instead of=20 ifconfig_lagg140_aliases=3D"inet6 2a01:75c0:1000:140::/64 anycast" I wrote ifconfig_vlan140_aliases=3D"inet6 2a01:75c0:1000:140::/64 anycast" so the IPv6 address was not set after reboot. This fails to get noticed, due the long lifetime of the announced = prefix. (the error has been visible since a few days only, I had no time to = investigate) So I can confess, plain 12.2-STABLE is no broken.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007601d6e2be$8acf3fb0$a06dbf10$>