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!
donawalt
Aug 01, 2022Mentor - Experienced User
Not enabled
FURRYe38
Aug 01, 2022Guru - Experienced User
Would you enabled it and then monitor the uptime?
This should stop the mysterious reboots.
- cdystheAug 01, 2022Virtuoso
FURRYe38 I am back! I took a break from Netgear and used an Asus router for a while. But I am a Netgear guy so I went and bought an Orbi 852 system thinking this newer model would have the IPv6 issue resolved by now. I was wrong. It does still have the issue! Has there been development here? I now have some time to spend on this since so what do I do now to help getting this resolved once and for all? Have a look at this thread:
https://www.dslreports.com/forum/r33241126-Netgear-IPv6-Problems-With-Comcast
The thread went on "forever" and went nowhere but someone said: "I believe they found a problem with IPv6 DHCP renewal". And that is exactly what I think the problem is! DHCPv6 is not working correctly on Netgear devices so the IPv6 address is dropped when the lease is out and the IP is renewed. Currently that seems to be every 4 days on Xfinity in my area, and every 4 days I lose my IPv6.
Now what? 🙂
- FURRYe38Aug 02, 2022Guru - Experienced User
We don't have any new info. Nothing from NG.
Seems that between you and donawalt your seeing quicker failure rate than he has.
Is Email logging enabled on your system when you were using it as your main router?
Ya seems that for unknown reason the renewal isn't happening or being handled badly. What that cause is, needs to be determined if it's being caused on the ISP side and the RBR isn't handling it right or if the problem is only with the RBR handling. Being that donawalt has seen more up time with IPv6 on there system and your not, almost wanna say this is a contention between bad ISP services and bad handling on the RBR.
You and donawalt also have different modem models as well so this could also play a role.
cdysthe wrote:
FURRYe38 I am back! I took a break from Netgear and used an Asus router for a while. But I am a Netgear guy so I went and bought an Orbi 852 system thinking this newer model would have the IPv6 issue resolved by now. I was wrong. It does still have the issue! Has there been development here? I now have some time to spend on this since so what do I do now to help getting this resolved once and for all? Have a look at this thread:
https://www.dslreports.com/forum/r33241126-Netgear-IPv6-Problems-With-Comcast
The thread went on "forever" and went nowhere but someone said: "I believe they found a problem with IPv6 DHCP renewal". And that is exactly what I think the problem is! DHCPv6 is not working correctly on Netgear devices so the IPv6 address is dropped when the lease is out and the IP is renewed. Currently that seems to be every 4 days on Xfinity in my area, and every 4 days I lose my IPv6.
Now what? 🙂
- cdystheAug 02, 2022Virtuoso
FURRYe38 wrote:We don't have any new info. Nothing from NG.
Seems that between you and donawalt your seeing quicker failure rate than he has.
Is Email logging enabled on your system when you were using it as your main router?
Ya seems that for unknown reason the renewal isn't happening or being handled badly. What that cause is, needs to be determined if it's being caused on the ISP side and the RBR isn't handling it right or if the problem is only with the RBR handling. Being that donawalt has seen more up time with IPv6 on there system and your not, almost wanna say this is a contention between bad ISP services and bad handling on the RBR.
FURRYe38 I had normal logging enabled on my old RBR 752 but never saw anything unusual there. Everything runs smoothly except for renewal of IPv6. I have now given a Comcast tech all my account information and he will check this from their side, but last time I spoke to Comcast their conclusion was that my Netgear CM2000 "wasn't updated" whatever that means and gave me the number for Netgear. My modem has the exact firmware version that it should have on Xfinity.
I do have another modem here, a Motorola MB8611 which is very similar to the CM2000 as far as specs go. Do you think I should try that? I am just afraid that if I put in the new modem I will not be able to re-enable the CM2000 if the problem isn't the modem.
Btw, right now even when I get an IPv6 address I do not get IPv6 connections so it's worse now for some reason. Maybe because Comcast are messing with my connection?
- donawaltAug 01, 2022Mentor - Experienced User
FURRYe38 :
Would you enable it and then monitor the uptime?
This should stop the mysterious reboots.
-------
How about this - reading that thread, I realized I had changed the log to include "Router operation (startup, get time etc)" - which I had always left unchecked, as it's mostly tons of DHCP messages. So, if the log is filling up, first now, I turned that setting off again. From past history, I will be lucky to have 2 log entries in the next month. So maybe log filling up causes mysterious reboots, which may be why I had one today from my log filling up?
I'll monitor uptime daily too...sound good?
- FURRYe38Aug 02, 2022Guru - Experienced User
So do you have email logging enabled or just deselected one of the logging items?
- donawaltAug 02, 2022Mentor - Experienced User
FURRYe38 I just deselected one of the log choices that adds about 99% of the entries in the log file. I did not enable email log sending, because frankly on my network with this set up there will be virtually nothing to send. I suspect this solves any chances of mysterious reboots for me, pointing to the same issue - log gets full, restart occurs. It can be solved by users for now by emailing the log and clearing it, or in my case, don't let entries go into the log. I bet it works! If not I'll try the email logs.