[SOLVED] No routing of IPv6 with Stateless/stateful DHCPv6 WAN client

[khit93]

Hi
For a little over 6 months I have had a system running, which got a fixed IPv4 over DHCP from my ISP and similarly it was assigned an IPv6 over DHCPv6 as well.
They do however not use prefix delegation and as with most ISP support options, they will only support their own routers. Looking around I managed to find information (although it was for pfSense) on someone who got it working to have the ISP give out the assigned /48 IPv6 prefix by setting some options in the advanced section of the DHCPv6 client on the WAN interface.
It worked fine, although I had to do a packet capture and extract the assigned prefix using wireshark and assign static /64 subnets to my internal networks.
A few weeks ago my ISP rolled out a configuration change, which for some reason broke the IPv6 routing in both directions. I reached out to their support and they informed me that "they have changed their data transmission protocols and you need to configure your router to use DHCPv6 (stateless/stateful) - dynamic IPv6-adresses". From what I can see it is not DHCPv6 Prefix-Delegation and therefore my current configuration should still be valid

In OPNsense, I have my DHCPv6 client set to advanced and under interface statement, I have defined the following Send options:
ia-pd 1, ia-na 1
I have also enabled Non-Temporary Address Allocation and assigned id-assoc na ID as 1 and also set Address IPv6-address as ::/0
Prefix Delegation is enabled and set id-assoc pd ID to 1 and Prefix IPv6-Prefix is set to 48.

What would I need to change in order to get IPv6 working again and is there any information that I need to request from my ISP?

[meyergru]

Try these instructions first before even fiddling with advanced DHCPv6 client settings. It is unlikely that your ISP changed their setup to something even stranger than before - probably they adhere to standards now. You can look at the logs to see what your ISP actually gives you if something does not work.

[khit93]

Found the issue to be related to the ISP still having some issues that were resolved after another outage yesterday and compared configurations with another user here: https://forum.opnsense.org/index.php?topic=46120.0