DHCPv6 Client Broken in latest snapshot
-
@mattund It looks like you are onto something. I was in communication with a couple of the developers who reviewed the commit that you referenced, so I sent them an email.
-
@mattund I tried the steps you posted and immediately saw the IPv6 gateway come back online on the Dashboard.
I rebooted and lost IPv6 again so I went to System / Advanced / Networking and disabled Hardware Checksum Offloading. Looking at the output of ifconfig this definitely removed the IPv4 offloading as well but it seems to give me IPv6 that persists across reboots.
Interestingly, I still don't seem to have any IPv6 for my clients.
EDIT: Looks like the prefix size got reset somehow. I set that properly and I am back in business minus hardware offloading.
-
@bimmerdriver Thank you!
@kmo12345
I'm glad it helped
-
I was able to reproduce the checksum disable box not actually disabling IPv6 transmit checksums, I opened an issue for that here: https://redmine.pfsense.org/issues/8980
-
@jimp A patch has been posted on https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231797 for this issue.
-
@bimmerdriver said in DHCPv6 Client Broken in latest snapshot:
@jimp A patch has been posted on https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231797 for this issue.
I opened https://redmine.pfsense.org/issues/9019 to pull in that patch, thanks!
-
@jimp The patch was committed: https://svnweb.freebsd.org/changeset/base/339585. Any idea when there will be a build with it?
-
No ETA at the moment, but we'll get to it before -p1.
-
I was experiencing the same issue. Running the ifconfig hn0 -txcsum6 command while also ticking the option in System / Advanced / Networking did the trick.
Hopefully the patch gets rolled into a build soon. I don't want to forget to set this if I reboot.
-
I updated to the latest snapshot on my test system yesterday. IPv6 is working again. I noticed the update from Renato (https://redmine.pfsense.org/issues/9019) where it says, "FreeBSD r339863 was cherry-picked to RELENG_2_4_4". I guess it's safe to say the fix is in the latest snapshot and it's working.
-
Great news! Thanks for testing
