Re: IPv6 neighbor flaps for ISP router are occurring frequently

From: Chris Ross <cross+freebsd_at_distal.com>
Date: Thu, 19 Sep 2024 17:43:00 UTC

> On Sep 17, 2024, at 14:46, Chris Ross <cross+freebsd@distal.com> wrote:
> 
> 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’s now been
> 7 hours since there have been any such notices from dhcpcd.  And, I can’t
> think of what couple. hanged. dhcpcd has been running for 15+ hours,
> complained for 8 hours, then stopped for 7.  I’ll keep an eye on it, but
> suffice to say I’m 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’t working.
The next-hop and router seems to be unreachable now.

All “route monitor” 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’m 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’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