radvd stops announcing IPv6 prefix after a while (radvd freeze?)

[marjohn56]

I was a little concerned as I said to you that when I created the rtadvd patch there appears to be features in radvd that have no equivalent in rtadvd. However, after a couple of months of people running it there seems to be nothing that doesn't work the way it should. I've just added a second commit to allow for remote log functions to work.

[IsaacFL]

I was looking through the old changes and from what I could tell from the comments, the reason pfsense moved from rtadvd to radvd, was they were having problems with CARP and VIPs in ipv6 at the time with rtadvd.  Maybe rtadvd has solved the issues from back then.

It is possible that from FreeBSD 11 to 12, something else in the network stack introduced a dependency on rtadvd.

[samsonmcnulty]

I was looking through the old changes and from what I could tell from the comments, the reason pfsense moved from rtadvd to radvd, was they were having problems with CARP and VIPs in ipv6 at the time with rtadvd.  Maybe rtadvd has solved the issues from back then.

It is possible that from FreeBSD 11 to 12, something else in the network stack introduced a dependency on rtadvd.

I was just having issues in a lab set up with rtadvd and carp vip's. Not sure it isn't kvm and virtualized network related but it definitely seemed to be a contributing factor.

Sent from my Pixel 4 XL using Tapatalk

[marjohn56]

With CARP etc, it's likely that RTADVD needs to be signalled to stop listening on the interfaces and only become active when needed, that's shouldn't be too difficult to implement if RTADVD became the default daemon. CARP isn't something I play with, so I've not looked into it.

[blusens]

I've been using the cron script to restart radvd and dhcpv6 since 2020. I've been on 22.1 for a few weeks and hadn't the issue anymore. Yay!