No IPv6 after upgrade to 23.01

[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.