Date: Thu, 19 Sep 2024 13:43:00 -0400 From: Chris Ross <cross+freebsd@distal.com> To: freebsd-net@freebsd.org Cc: Karl Denninger <karl@denninger.net> Subject: Re: IPv6 neighbor flaps for ISP router are occurring frequently Message-ID: <80124FC7-3C96-489C-803D-D0310FBA3D05@distal.com> In-Reply-To: <C9F6C11F-A0E9-4E39-B56E-5F5D564D0021@distal.com> References: <89F4F5A4-E3D9-4A43-84F6-908E3FA221A6@distal.com> <83BCC913-3375-4847-B720-5F06D76F6646@distal.com> <c26dc20a-c6c9-454c-8763-ae21d8b68b20@denninger.net> <6CFC398B-BC5C-4CFC-8733-8D9732B121CA@distal.com> <C9F6C11F-A0E9-4E39-B56E-5F5D564D0021@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sep 17, 2024, at 14:46, Chris Ross <cross+freebsd@distal.com> =
wrote:
>=20
> Hmm. Well, I updated my releng/14.1 tree and built a new kernel last =
night.
> I rebooted and after dhcpcd started up it was emitting the same =
notices
> for many hours. But, at about 07:30 this morning it stopped. It=E2=80=99=
s now been
> 7 hours since there have been any such notices from dhcpcd. And, I =
can=E2=80=99t
> think of what couple. hanged. dhcpcd has been running for 15+ hours,
> complained for 8 hours, then stopped for 7. I=E2=80=99ll keep an eye =
on it, but
> suffice to say I=E2=80=99m perplexed.
Alright. Coming back to this, I was clearly not paying attention. At =
the
time I stopped seeing the aforementioned problem, a new one started. =
There
seemed to be some sort of link flap on my local interfaces a couple
of times the morning of Sept 17, and after that IPv6 wasn=E2=80=99t =
working.
The next-hop and router seems to be unreachable now.
All =E2=80=9Croute monitor=E2=80=9D has been showing me of late is:
12:59:49.473 PID 0 delete neigh fe80::3e8a:b0ff:fe3e:4dce%vlan0 state =
INCOMPLETE iface vlan0
12:59:53.522 PID 0 delete neigh fe80::3e8a:b0ff:fe3e:4dce%vlan0 state =
INCOMPLETE iface vlan0
12:59:57.450 PID 0 delete neigh fe80::3e8a:b0ff:fe3e:4dce%vlan0 state =
INCOMPLETE iface vlan0
I restarted dhcpcd, and it acquired an address reportedly from this same
peer. Well, maybe I=E2=80=99m wrong and it just reestablished based on =
the
prior delegation:
Sep 19 12:39:25 logrus dhcpcd[50864]: main: pidfile_lock: =
/var/run/dhcpcd/pid: Permission denied
Sep 19 12:39:29 logrus dhcpcd[52739]: dhcpcd-10.0.10 starting
Sep 19 12:39:29 logrus dhcpcd[53589]: DUID =
00:01:00:01:2e:3e:5e:7f:a4:53:0e:79:b9:82
Sep 19 12:39:29 logrus dhcpcd[53589]: vlan0: IAID ff:00:00:06
Sep 19 12:39:29 logrus dhcpcd[53589]: vlan0: IA type 25 IAID 00:00:00:00
Sep 19 12:39:29 logrus dhcpcd[53589]: vlan0: rebinding prior DHCPv6 =
lease
Sep 19 12:39:29 logrus dhcpcd[53589]: intnet1: activating for delegation
Sep 19 12:39:29 logrus dhcpcd[53589]: intnet1: IAID ff:00:00:05
Sep 19 12:39:29 logrus dhcpcd[53589]: intnet2: activating for delegation
Sep 19 12:39:29 logrus dhcpcd[53589]: intnet2: IAID ff:00:00:03
Sep 19 12:39:29 logrus dhcpcd[53589]: intnet3: activating for delegation
But, in either case, I still have a default inet6 route, but it isn=E2=80=99=
t
working because the next-hop seems to be unreachable. :-/
As much of an IPv6 fan-boy as I am, even I am thinking this is
just a PITA. ;-)
- Chris=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80124FC7-3C96-489C-803D-D0310FBA3D05>