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...
There has been long standing IPv6 issues on Orbi AX since v4 intro'd and hasn't been fully addressed.
We have passed all this up to NG for review. It's mostly in there ballpark. The other part is the ISP consideration, as there are some ISP service issues that has been observed that also plays a roll in all this as well. So this is a 2-sided problem and both NG and ISP need to come to the table. We have been pushing this as best as we can where we can.
All I can say.
"Yeh! What FURRYe38 says!!"
BUT . . . It'll all be in Netgears' court to deal with. And they have and can. Being an ex-Telco person and having had these kinds of services since the mid-90's, the manner in which Telco's deploy something like IPv6 is going to be the most minimal and cheapest manner as possible. Which 6rd and some other versions are. But with my CL Fiber 6rd worked perfectly on my 853 until about halfway through v3 FW on these things when changes were made somewhere that did show up in the IPv6 UI as text and info presentation changes. So we know that they have done it, can do it and do it well. But isn't now. If it does it's not for long.
It's working great and long term on my Nighthawk MK-83.