Is IPv6 Dynamic prefix not updating (after losing WAN) still a thing in 24.x?

[Cyberturtle]

Hi all,

long time no see. I just came back as I'm still thinking of switching back to my custom device with OPNsense. In the past I had issues with IPv6 not updating the prefixes after WAN connection lost (due to ASSIA profile enhancement or nightly reconnect). I've spent a lot of time of testing during a few 23.x releases but at the end I sadly had no more time for further testing and stopped testing back in June 2023.
So how is the current situation? Do you experience still problems? I'm running a dual stack connection from Deutsche Telekom.

Thanks in advance.  :)

[citydweller]

Still the same problem here, using OPNsense 24.1.6. After a manually reconnect or auto reconnect ever 24h hours, the clients won't get notified about the new prefix nor get a new IPv6 address.

[Wirehead]

Technically speaking, ISP's shouldn't be doing dynamic IPv6 prefixes (care to share the ISP?).

That said, is it the interface -tracking- the WAN, or the WAN not getting a new IPv6?

[Cyberturtle]

But there are many providers in Germany using dynamic prefixes due to privacy concerns.

All tracked interfaces and the clients connected to are losing IPv6 connection.

During testing pfSense it wasn't an issue too. But I don't want to use pfSense as I don't like how the company is acting and I'd like to support the OPNsense community as well.

Currently I'm testing an UniFi router as a replacement for my Fritzbox.Both are capable of handling dynamic prefixes.

[Wirehead]

Ok, but is it the interface -tracking- the WAN, or the WAN not getting a new IPv6?

If you login via SSH to your opnsense appliance when such an event occurs, and you choose option 8 "shell", and then type:
ping -6 google.com (ctrl+c to cancel)

-> Do you get replies?
If yes, it indicates that on the WAN side things would be fine and it's your tracking of the WAN going wrong.
If no, it indicates that it's the WAN not refreshing.