NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
[BUG] IPv6: 6rd support breaks after an IPv4 change
Hello, For context, I'm using CenturyLink fiber, which offers IPv6 through 6rd. The problem: with 6rd, IPv6 autoconfig works only on the initial connection. It does not happen on subs...
Netgear somehow provided me with a trial firmware that fixed the issue back in September 2023. They've emailed me recently to ask me to try the new official release, which I just did. The new firmware release is still broken. I wish I had kept the trial version.
I'm now running a script on my raspberry pi that continuously tries to detect the bug, and reboots the Orbi when it is hit.
I've received DMs on other forums from a few other people impacted by this. I am now giving them by detection/reboot script. I'm not sure if anyone from Netgear is reading this, but 14 months later this is just sad lol. Support case 47156485
What Firmware version is currently loaded?
What beta FW version did you get that seem to fix what you were seeing?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?Have you tried a custom IPv6 DNS address vs decteded ISP IPv6 DNS?
Hey - I replied to your DM where you asked some of these questions.
Note that the bug has been independently reproduced by BugCrowd through the Netgear bug bounty program. They used their own hardware to reproduce (probably in a black box environment - no ISP, no ONT). This is purely a firmware issue - IPv4 address changes aren't properly handled by the IPv6 stack. The Netgear support case (and Bugcrowd submission) has all the details
OK sounds good.
Will get this to NG and see if we can get some more traction on it.
Ya the fix in the beta they gave you didn't get into following released versions. Wondering why. 🙄
See what we can do.
