NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
donawalt
Apr 03, 2022Mentor - Experienced User
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...
- Jul 07, 2022
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!
CrimpOn
May 30, 2022Guru - Experienced User
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.
donawalt
May 30, 2022Mentor - Experienced User
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.
- cdystheMay 30, 2022Virtuoso
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..
- donawaltMay 30, 2022Mentor - Experienced User
I wish there was some workaround, even on the Comcast side.
- cdystheMay 30, 2022Virtuoso
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.
- donawaltMay 30, 2022Mentor - Experienced User
For me last week, it happened in 3 hours. Sometimes I got 3 days, sometimes less than a day.
- donawaltJun 01, 2022Mentor - Experienced User
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.
- cdystheJun 01, 2022Virtuoso
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.
- donawaltJun 01, 2022Mentor - Experienced User
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?
- FURRYe38Jun 01, 2022Guru - Experienced User
It's in NG ball park. 😉