NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ipV6 disconnecting on Orbi RBR850
(NOT RBK53 model in drop down, why is RBR850 not there?) I have RBR850, firmware V4.6.7.13_2.1.9, and a CM1200 modem connected to Comcast's 1.2/40 service. All is working well, speeds, modem numb...
OK, it's been two weeks, and my IPv6 has been working perfectly all that time, no more disconnects! I am going to mark this thread as solved, with the update of firmware to 4.6.8.5 being the thing that fixed it. If others are still having trouble I suggest starting a new thread, as there may be multiple issues. Thanks everyone for your help!
donawalt wrote:I still have this problem too, and I also think it has something to do with renewing IP address - as the tests will say no valid IP address or something similar. Orbi reports having a LAN and WAN IP address, so the only answer seems to be the IP addresses are no longer valid at Comcast.
I too wonder why this is taking so long to fix.
I think it's a DHCPv6 on WAN issue. Comcast/Xfinity changed something in February of this year which broke DHCPv6 in certain Netgear devices. That is exactly when this started to happen on my Orbi system. This thread makes me almost sure that that's the issue:
In that thread it says:
"Yes, the Xfinity DHCPv6 PD servers appear to have shifted behavior, they now communicate via global IPv6 addresses exclusively...."
Would really like a comment on this from Netgear even if it is that I am completely off my rocker! 🙂 We are closing in on half a year with broken IPv6 on my system. That is not good.
FURRYe38 is there any way you can get Netgear staff to look at this and reply? They are the only ones who can address this on our behalf, they are the only ones who know how their code interacts with comcast. We need a solution to this, or st least an expectation that it is seriously being investigated. IPv6 is unusable as it stands for those affected.
I've already passed this on to NG for review back in Jan and March. It's in there hands.
donawalt wrote:
FURRYe38 is there any way you can get Netgear staff to look at this and reply? They are the only ones who can address this on our behalf, they are the only ones who know how their code interacts with comcast. We need a solution to this, or st least an expectation that it is seriously being investigated. IPv6 is unusable as it stands for those affected.
I have a suspicion that the problem relates to how DHCPv6 is handled by your specific ISP, perhaps even the specific DHCP server for your local area. If this is the case, Netgear will have a devil of a time reproducing the problem. I can just imagine an engineer remarking, "some bozo thinks that our router does not work with Xfinity DHCPv6. I have an Xfinity connection in the lab here in San Jose and it works great! Stop wasting my time!"
(Because I have no other hobbies...) I have been able to document that in the case of my Spectrum connection, DHCP works exactly as it is supposed to.
- Spectrum gives me a 24 hour (86,400 seconds) DHCPv4 lease and
- a one week (604,800 seconds) DHCPv6 lease.
- At exactly 12 hours, the Orbi does a DHCPv4 renew and within 0.12 seconds, Spectrum extends the lease another 24 hours.
- At almost exactly 3.5 days, Orbi does a DHCPv6 renew and Spectrum responds, although not as quickly.
- There is also "more going on" with DHCPv6 in terms of information requests from the router and responses from Spectrum.
This required an investment in a gigabit switch (Netgear GS108Ev3) that I placed between the modem and router.
(I wanted a 5 port, but on the day I purchased the switch, the Amazon price was lower for 8 ports than for 5 ports. Today, a 5 port switch costs less.)
Then connected one of the other gigabit ports to my PC.
Told the switch to mirror the router port to the PC.
Set up Wireshark with a Capture filter for (port 67 or port 68 or port 546 or port 547).
Wait... and wait.... and wait. (I ran one capture for eight days in order to verify that DHCPv6 renewed every 3.5 days.)
The point is that capturing the actual data exchange between router and (Comcast/Xinity, correct?) provides evidence.
The actual data packets exchanged between router and ISP.
Wow interesting, thanks. The reality is though, as a customer if it doesn’t work, customers will move to another router when they need IPv6. And it’s not an isolated problem, based on netgear-reddit-comcast forums.
CrimpOn wrote:I have a suspicion that the problem relates to how DHCPv6 is handled by your specific ISP, perhaps even the specific DHCP server for your local area. If this is the case, Netgear will have a devil of a time reproducing the problem. I can just imagine an engineer remarking, "some bozo thinks that our router does not work with Xfinity DHCPv6. I have an Xfinity connection in the lab here in San Jose and it
...
The point is that capturing the actual data exchange between router and (Comcast/Xinity, correct?) provides evidence.
The actual data packets exchanged between router and ISP.
So now we know what's wrong. Thank you so much for a really thorough investigation! We have developers of browser software on this Orbi network who has to have IPv6 work and I do not want to have to manually update the IP every week like I am doing now so we are close to giving up and get something else here for now.
So what's next steps? The easiest would be for Netgear to talk to Comcast to find out what changed at the beginning of the year I do not know how this works between ISP's and providers of networking hardware. I know that if I talked to Comcast/Xfinity they would just tell me to use their stuff and everything would work.
I really hope it can be sorted out since the Orbi system works great except for this issue.
donawalt wrote:Wow interesting, thanks. The reality is though, as a customer if it doesn’t work, customers will move to another router when they need IPv6. And it’s not an isolated problem, based on netgear-reddit-comcast forums.
Yes, I have seen this issue on Reddit, in another thread here and on both DSLReport and Xfinity forums. So this is not isolated to us here in this thread..
I wish there was some workaround, even on the Comcast side.
donawalt wrote:I wish there was some workaround, even on the Comcast side.
The only "workaround" is to manually disable IPv6 > Enable IPv6 with Autodetect > Wait 5 minutes > Set IPv6 to DHCP. Kinda ridiculous having to do this once a week when IPv6 drops. It mostly happens on weekends though which is good I guess?
I'm sure Xfinity/Comcast could work this out with Netgear quite easily. The question is will they, and if yes to that, when? I mean, I use a Netgear CM2000 modem approved for use on my XFinity gigabit connection so there must be some line of communication between the two.
For me last week, it happened in 3 hours. Sometimes I got 3 days, sometimes less than a day.
I just tried another test - activated IPv6 on Monday 5:30 PM EDT. I last checked it today, Wednesday 7:30 AM EDT, and it was fine. Now at 12 PM EDT, it fails all tests from test-ipv6.com and others - so it fails 38-42 hours or so later. Here is the test-ipv6.com detailed test results, in the images below. Yet the last image shows everything looking as it always does on the IPv6 advanced config page for the router. This is shameful we have gotten non reply from Netgear.
Yes, this is not good. I have never managed a network where a protocol/service just stops working and I have manually bring it back up once a week or more. I have been a Netgear nut for many years. I even bought a CM2000 modem instead of whatever Xfinity tries to push so I am heavily invested (literally) in Netgear. It's wearing a bit thin now.
I am happy to test something if Netgear wants to, if it's local to some areas and not others based on some rollout of Comcast servers, for example. This has to get fixed, this is a show-stopper if it won't ever get resolved.
FURRYe38 any chance of getting some sort of update or communication since you referred this to them months ago? I thin we deserve that, don't you?
It's in NG ball park. 😉
