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!
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.
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.