No IPv6 after upgrade to 23.01

maverickws

@jasonreg
Sometimes after doing a lot of configuration changes, giving a reboot on the firewall gets everything running perfectly at last.
It could also mean your IPv6 upstream gateway doesn't respond to monitoring. In that case you either mark the GW always up, or get a valid IPv6 address for the Gateway monitor to reach and define its state.

About my previous attempts to figure this out and following up on @mhillmann's conversation;

I have data from over a year back where I can see my IPv6 gateway with this ISP. My IPv6 address is always one of a /40 pool, and the upstream gateway is always the same. I checked this extensively.

So the WAN interface was using DHCPv6 but in Routing the selected IPv6 gateway was the static one I created. I actually went a step further and disabled the dynamic gateway on the routing table.

So the static gateway was up but no traffic from the machines which had an IPv6 correctly attributed by tracking WAN interface setup.

So I left this at a standstill waiting for a fix to the issue here. I resigned to "no IPv6" for a while.
The other day I opened a site which accused me of being using IPv6.

Made an IPv6 test: IPv6 working.
Tested on other machines: IPv6 working.

Checked the firewall, have the Static IPv6 gateway selected, the same configuration I left before when IPv6 wasn't working. And wasn't for many days.

Currently 17 days uptime, have no idea how the issue resolved by itself.

So in the meanwhile, tried just rebooting the firewall to see how'd it would go.
After reboot, no IPv6 again.

shadowking

Thanks for the redmine report, I'll disable IPv6 until a fix is released.

jordanp123

@shadowking
Yes, thank you everyone for the conversation. I didn't realize this thread existed and had created my own which appears to be a result of the same issue. I'm gonna disable ipV6 until we have a resolution.

jimp

FYI- The latest Plus (2.7.0) and CE (23.05) snapshots have a fix for this. See https://redmine.pfsense.org/issues/14072 for details.

tl;dr we added a flag to rtsold which always fires the script no matter which flags are in the RA.

It's working for me on the latest snapshots here in my lab, and I could reproduce the issue reliably before.

shadowking

@jimp thx for the hard work, I'll wait for the next stable release, but it's good to see that this issue has been handled quickly and properly.

jordanp123

@jimp
Just tried it in a CE snapshot VM, works perfectly. No issues at all, once Plus and CE are out in stable I'll be able to get rid of my "Kludges" to get V6 to work. Thanks Everyone Its much appreciated !!!!

mhillmann

Works flawless. Thank you for the solution!

jimp

Also noteworthy that we didn't just make the change locally, it's been submitted upstream to FreeBSD as well and will be in future releases there, so we don't have to worry about this breaking again in the future:

https://reviews.freebsd.org/D39931

mhillmann

@jimp Good choice, as the issue affects FreeBSD too, due to the way rtsold was originally coded in the OS. Rtsold worked before, because sometimes even coding errors produce the intended(?) outcome by mere luck.

jimp

@mhillmann said in No IPv6 after upgrade to 23.01:

@jimp Good choice, as the issue affects FreeBSD too, due to the way rtsold was originally coded in the OS. Rtsold worked before, because sometimes even coding errors produce the intended(?) outcome by mere luck.

On previous versions of pfSense we had a local patch to rtsold that ended up running the script for any flag combination but it looks like that may not have been intentional. So yes, it was working before but completely by accident.

But now it's working deliberately without a local only change. :-)

maverickws

Alright, the latest update simply broke IPv6 completely. I am not getting any IPv6 address at all, not just a gateway issue

jimp

That is likely unrelated. I tested the changes for this and I could reproduce it before the fix and it was working OK after. If there is a change in behavior it's probably not from this change specifically. Start a fresh thread and gather info there to debug it.

maverickws

@jimp thanks for your reply. You're probably right and already did here. Thanks!

shadowking

Works fine for me now, good job.