IPv6 no longer works after upgrade to 23.1.2 and 23.1.3

Started by snapilica2003, March 11, 2023, 08:39:08 AM

Previous topic - Next topic
March 11, 2023, 08:39:08 AM Last Edit: March 11, 2023, 08:54:49 AM by snapilica2003
I know that there are other similar topics about this but they all seem to have other types of issues and all the fixes there don't seem to work for me.

To get it a short explanation, I have a PPPoE connection that also sends out an IPv6 /56 network via DHCPv6. I then have 2 interfaces that use Track Interface. Everything was working just fine prior to these updates but then it seems that out of the blue the router itself loses its own /128 allocation, and all the tracked interfaces loose their own /64 network.

When going to Interface -> Overview -> WAN (pppoe0), I can see that there's still a /56 delegated prefix there, but there's no assigned /128 for the interface itself (and I don't have "Request only an IPv6 prefix" box checked), and all other interfaces don't have anything on the IPv6 network.

Can you help me troubleshoot this issue? Where exactly can I look for what is going on and why do I lose IPv6 all of a sudden?

Renewing DHCPv6 under the Overview page doesn't seem work reliably, Reloading PPPoE also doesn't seem to work reliably, restarting the router doesn't seem to work reliably. And when I say reliably, I mean that all of the above 3 might sometimes fix the issue and I do get IPv6 up and running, until next time when it fails again and I'm back to square 1 and it can be another fix that will temporarily work.

2023-03-11T09:29:38 Notice dhcp6c RTSOLD script - Sending SIGHUP to dhcp6c
2023-03-11T09:29:37 Notice dhcp6c dhcp6c REQUEST on pppoe0 - running newipv6
2023-03-11T09:29:36 Notice dhcp6c RTSOLD script - Sending SIGHUP to dhcp6c


Edit: Another thing I've noticed is that, whenever I reset the config or disconnect cable or anything that requires a pppoe reset, I do get everything working for a few seconds. I get the prefix delegation, I get an assigned /128 for the WAN interface, and everything is working for a few seconds, then everything is gone.

Is this issue now fixed for you? I'm on 23.1.7 and I'm attempting to get IPv6 to work with delegated prefix, DHCPv6 and ULA. So far it does not work at all, I have to reload DHCPv6 on WAN interface to even get the delegated prefix (/60) and it seemingly randomly decides to use it on the LAN interface or not, even though I have "track WAN interface" in IPv6 settings...

Same for ULA: I configured a virtual IP fd00::1 on LAN interface, but I can't figure out how to tell opnsense to also use it in DHCPv6. Manually DHCPv6 seems to only accept a /64 within the delegated range...

You can only assign a single IP using DHCPv6, if you want to use more than one, you need to use RA.

Thanks, I did just that, that helped for ULA.

I still have the problem that the delegated IPv6 prefix is not reliably acquired by opnsense, I don't know why, still looking into it.

It would be great to have DHCPv6 able to handle multiple IP ranges in opnsense. I made a feature request for this: https://github.com/opnsense/core/issues/6555