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
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?
FURRYe38
Aug 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.
- FURRYe38Aug 02, 2022Guru - Experienced User
Let us know what you find out. Would be interesting.
There seems to be a issue in the code though something about an increase to 1024 however the field values are still set for 3. So by limiting what you select in the logs may not see the problem for may only put off seeing the problem for a longer period of time before the bug is hit. 🙄
- donawaltAug 02, 2022Mentor - Experienced User
True, I have a reminder to check the log monthly and I have never seen more than about 3 entries in the log. So I bet it will be fixed before I see it, if it is related to a full log!
- cdystheAug 02, 2022Virtuoso
I have been in touch with Comcast/Xfinity on Reddit and they scheduled a tech to come to my house to look at this. I told them this may be a Netgear issue, but they are very interested in finding out what's going on. Talk about customer service from Comcast! I bet you haven't heard that too often! I wish Netgear were as responsive as that.
I will update here when I know more.
- FURRYe38Aug 02, 2022Guru - Experienced User
Also check the system uptime for any changes here. The email logging helps on this one.
donawalt wrote:
True, I have a reminder to check the log monthly and I have never seen more than about 3 entries in the log. So I bet it will be fixed before I see it, if it is related to a full log!
- FURRYe38Aug 02, 2022Guru - Experienced User
Ok sounds good...might ask them to review this thread as well for reference. Maybe we can collaborate on information. Would be good to know where the problem is coming in at. I dont' doubt it's a NG issue, just maybe additional things on the ISP side that could be also causing problems here.
cdysthe wrote:
I have been in touch with Comcast/Xfinity on Reddit and they scheduled a tech to come to my house to look at this. I told them this may be a Netgear issue, but they are very interested in finding out what's going on. Talk about customer service from Comcast! I bet you haven't heard that too often! I wish Netgear were as responsive as that.
I will update here when I know more.
- donawaltAug 17, 2022Mentor - Experienced User
RBS850/RBR850, just one day after I temporarily disabled it to do some testing and then re-enabled it. The router web page thinks it has an IP address, but no one else does. Firmware version V4.6.8.5_2.1.9.
- FURRYe38Dec 13, 2022Guru - Experienced User
Any updates on this?
- donawaltDec 13, 2022Mentor - Experienced User
Well it's funny you should ask FURRYe38 😉
I have been on V4.6.14.3_2.3.12 since it came out, maybe 2 weeks? IPv6 has been solid. Yesterday, I switched out my CM1200 modem and activated a Netgear CM2000 modem in its place. In the day since, IPv6 has been fine. What may be more important, is in the last 4-6 weeks, the only time I lost IPv6 was when some sort of update/upgrade/power cycle happened to the RBR850 router. I took that as a sign that things were better, but not 100% for me. My CM2000 has restarted in the last day, provisioning and stuff that happens with new modems on the Comcast network, and everything has been fine - no downtime. Fingers crossed!
- FURRYe38Dec 13, 2022Guru - Experienced User
Kewl. Keep us posted on this...like to know if you see any issues with the CM2000 modem.
Hoping IPv6 is getting better. Where this is happening is still not fully known or understood.
- donawaltDec 13, 2022Mentor - Experienced User
Will do!
- cdystheDec 14, 2022Virtuoso
I have very good news! I installed the FW update V4.6.14.3. I factory reset and set it up again. IPv6 dropped after an hour. I set it to DHCP and got another IP and it has stayed stable for more than a week now. So maybe the FW update did solve this problem. I have not had IPv6 connections for more than a year so I am hoping this fixed it.
I wish I knew in more detail what Netgear did in the latest FW upgrade. The changelog is not very detailed.
Anyway, very good news, at least for me! 🙂
- FURRYe38Dec 14, 2022Guru - Experienced User
Great news to hear. Hoping that some bugging with this issue at NG has done something good.
Glad it's working. Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System
Enjoy. 📡
cdysthe wrote:
I have very good news! I installed the FW update V4.6.14.3. I factory reset and set it up again. IPv6 dropped after an hour. I set it to DHCP and got another IP and it has stayed stable for more than a week now. So maybe the FW update did solve this problem. I have not had IPv6 connections for more than a year so I am hoping this fixed it.
I wish I knew in more detail what Netgear did in the latest FW upgrade. The changelog is not very detailed.
Anyway, very good news, at least for me! 🙂
- cdystheDec 14, 2022VirtuosoSo reset and restore settings is just as good as reset and enter settings manually?
- CrimpOnDec 14, 2022Guru - Experienced User
cdysthe wrote:
So reset and restore settings is just as good as reset and enter settings manually?No. They are different. The saved configuration MAY not copy "garbage that has collected" in memory. In that case, the reset clears the garbage and reinstalling the configuration is great. On the other hand, if the actual saved config file is corrupted, restoring it will restore the garbage. I prefer to spend 10 minutes taking a chance on restoration before committing to two hours of manual data entry.
- FURRYe38Sep 14, 2023Guru - Experienced User
Just checking to see if this is still a problem for you or not in new v7 released FW?
cdysthe wrote:
I have very good news! I installed the FW update V4.6.14.3. I factory reset and set it up again. IPv6 dropped after an hour. I set it to DHCP and got another IP and it has stayed stable for more than a week now. So maybe the FW update did solve this problem. I have not had IPv6 connections for more than a year so I am hoping this fixed it.
I wish I knew in more detail what Netgear did in the latest FW upgrade. The changelog is not very detailed.
Anyway, very good news, at least for me! 🙂