IPv6 PD not work after update OPNSense from 22.7.11->23.1_6

[Cyberturtle]

I'm no longer getting an IPV6 address detected by https://test-ipv6.com/ after updating to 23.1.8 from the previous most recent release. I attached a log that starts right after the update. Hopefully someone can help me figure out what's wrong with that.

Can you pleaese provide some screenshots of your configuration? Your logs describes problems forwarding IPv6 packets/request, but I don't know why. Dou you have static IPv6 leases/prefixes?

[Gobd]

Sorry I'm not sure which parts of my config you'd want screenshots of, hopefully a slightly redacted config backup will work. If not let me know which config pages you'd want screenshots of and I'll be happy to provide.

I found another post that said saving the WAN interface again fixes this. It did fix https://test-ipv6.com/ but it broke again after a restart. Also the routing problems were still showing up in the log even though it reported IPV6 was working.

Also getting "failed to create listening socket for port 65354: Address already in use" again. It seems every every restart I have to change the listen port for dnsmasq for it to start up.

[Cyberturtle]

So if it's not wirking after a restart and after saving the interface a IPv6 DHCP log could be helpful. You can change the log level under Interfaces -> Settings -> IPv6 DHCP log level to Debug.
I have had a look into you configuration, but screenshots will help a lot more of:

• Interfaces: WAN
• Interfaces: LAN
• Interfaces: Overview WAN and LAN

Keep in mind to remove credentials from your screenshots as well parts of the IPv6 prefixes for privacy.
Meanwhile you could try the "Prevent Release" option under Interfaces -> Settings -> IPv6 DHCP Prevent release and check it and reboot.
What shows your logfile under System -> Log Files -> General when you search for dhcp6 and selecting Debug?

[dfw3xam1n3r]

Update: whatever was fixed regarding IPv6, DHCPv6 and delegated prefixes in the 23.1.8 update seems to have resolved my IPv6 dropping issues. I rebooted afterward and at the very least, so far, have not had to touch it. It just works. 

[franco]

You mean 23.1.9?


Cheers,
Franco

[dfw3xam1n3r]

Yeah I updated mid-typing.

[franco]

Ok, thanks. No concrete complaints from IPv6/23.19 combo yet.. looks like we are one step further now.


Cheers,
Franco

[Gromhelm]

Just updated to 23.1.9 and Yes! All green lights on https://test-ipv6.com/ !

Your readiness score 10/10   for your IPv6 stability and readiness, when publishers are forced to go IPv6 only

Nothing changed in the configuration. I did see an error regarding IPv6 prefix update in the logs after update, and Unbound failed to start automatically, but everything was fine after manually starting unbound (see my description of this on GH).