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...
I have CL Fiber and have been through exactly what you describe many times. 6rd is the easiest and cheapest way to deploy "fakish" IPv6. And depending on what the area you are in was previously setup the settings and format may be different. But if you know that it's 6rd, you're a third of the way there. Even setting it up in their own routers is a bit of a job.
There is a set group of settings that your dynamic IPv4 Address won't affect. It directs you directly to the IPv6 servers. You may already have it, but please find them attached. I use them on all my gear and depending on which Router System you're using they will behave differently. On my Orbi RBK853, IPv6 worked like a charm until a FW update halfway through v3.x. Since it's work for a while then nothing. On an MK-X3 system I have had it up and running for a long time. So . . .
But this has been discussed in depth and we'll make sure the discussion keeps going and pertinent info gets passed on. Cuz we're all goin' to need it last week.
Hope this helps.
FarmerBob1 wrote:I have CL Fiber and have been through exactly what you describe many times. 6rd is the easiest and cheapest way to deploy "fakish" IPv6. And depending on what the area you are in was previously setup the settings and format may be different. But if you know that it's 6rd, you're a third of the way there. Even setting it up in their own routers is a bit of a job.
There is a set group of settings that your dynamic IPv4 Address won't affect. It directs you directly to the IPv6 servers. You may already have it, but please find them attached. I use them on all my gear and depending on which Router System you're using they will behave differently.
Yeah I have no issues setting up 6rd - as stated in my first message, it works fine for about a week (until IPv4 gets renewed), due to the bug I described. Not sure if you read my message completely, or if you mention it for others just in case.
Anyway - some people may or may not experience what I describe, as it all depends on how often CenturyLink (or your ISP) changes our IPv4. For almost a year I had no issues because my IPv4 was never changing. In the past few months, CenturyLink seems to have rolled out a change that causes IPv4 leases not to be renewed, with a new IP getting issued every week or so. (there's also the possibility of a recent Orbi firmware update that caused the Orbi to stop renewing DHCPv4 leases, causing new ones to get issued by the ISP). Whatever the cause is, unfortunately that makes the Orbi 6rd bug described above a real issue due to the interaction between IPv4 and 6rd.
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.
