I have a routing problem after update from 23.1.4_1 -> 23.1.5_4. First thing was that I had an exception (which I could not read before it was replaced by the reboot notice). The reboot did not occur, I had to manually restart the box.
After coming up again, router advertisements were being handed out, I could see the addresses, but no IPv6 routes. After a manual restart of radvd, the routes re-appeared.
Could have something to do with resequencing of events during interface startup. In my case, the WAN interface does not have a routeable IPv6, since I get only a prefix range via DHCPv6.
I have a similar problem. see my post here.
https://forum.opnsense.org/index.php?topic=33351.0 (https://forum.opnsense.org/index.php?topic=33351.0)
Cancel that - this was not a routing problem after all. radvd is fine, as are the routes. I wonder why a radvd restart fixed my problem, though.
Matter-of-fact, what is problematic is dnsmasq, which is what I use instead of unbound.
Right after the box comes up, it seems that dnsmasq is started before it can reach external servers (probably because internet connection was not up yet). Thus, OpnSense cannot resolve any names.
When I restart dnsmasq, everything is up and running again.