NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Re: RBR750 turns to waiting status everyday
Has anyone ever figured this out. I seem to get this but every few months on my RBR 750. It happened this evening and for the first time I didn't immediately reboot my or is (and still haven't). Ba...
What Firmware version is currently loaded?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Be sure your using a good quality LAN cable between the modem and router. CAT6 UTP is recommended.
How many RBS are deployed?
What is the size of your home? Sq Ft?
Has this worked before on prior version of FW?
Been postings about v.31 not working well for users. v.21 is most stable to date.
What Firmware version is currently loaded?
V7.2.6.31_5.0.24
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Huawei OptiXstar HG8010Hv6
Be sure your using a good quality LAN cable between the modem and router. CAT6 UTP is recommended.
Yes I have CAT 6 throughout the house.
How many RBS are deployed?
1 Router and 2 Satellites
What is the size of your home? Sq Ft?
2200 sq ft
Has this worked before on prior version of FW?
Been postings about v.31 not working well for users. v.21 is most stable to date.
I see some previous threads where I had firmware V7.2.6.21_5.0.20 and also had the issue where if there was loss of internet connectivity, the routers were not able to reconnect themselves without (in the previous case) rebooting them.
So it seems to be a general thing for me across versions, human intervention always fixes the internet connectivity where I think there has to be some form of basic logic built into the router itself to do this. If it did it could be that we don't need to do any of these human reboots or clicking on test / apply to fix the issue.
Do you know has Netgear ever considered this. I did post this idea of at least some option to switch on such internal retry logic but I guess it was never considered as of yet.For now I'm going to put some sort of auto reboot mechanism into my homeassistant server which has a netgear integration that seems to have the ability to reboot a netgear router so I'll try; to implement some logic there to try at least 1 reboot if it ever gets into a similar state of loss of internet connectivity for > x minutes, try 1 reboot (maybe max 1 per day or something to stop it endlessly rebooting in cases where the internet is genuinely down).
But I think this has to be a very basic thing that has to be put into these routers to be honest, otherwise I can only see people lose faith in their robustness (even if in this case it was perhaps a 1 second blip in my actual internet providers connectivity).
mark0077 wrote:
What Firmware version is currently loaded?
V7.2.6.31_5.0.24
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Huawei OptiXstar HG8010Hv6
No router here but maybe some routing behind the scenes going on. This seems like a fairly new ONT system.
Be sure your using a good quality LAN cable between the modem and router. CAT6 UTP is recommended.
Yes I have CAT 6 throughout the house.
How many RBS are deployed?
1 Router and 2 Satellites
What is the size of your home? Sq Ft?
2200 sq ft
For that size of home, only the RBR and just one RBS would be needed.
Has this worked before on prior version of FW?
Been postings about v.31 not working well for users. v.21 is most stable to date.
I see some previous threads where I had firmware V7.2.6.21_5.0.20 and also had the issue where if there was loss of internet connectivity, the routers were not able to reconnect themselves without (in the previous case) rebooting them.
So it seems to be a general thing for me across versions, human intervention always fixes the internet connectivity where I think there has to be some form of basic logic built into the router itself to do this. If it did it could be that we don't need to do any of these human reboots or clicking on test / apply to fix the issue.
Do you know has Netgear ever considered this. I did post this idea of at least some option to switch on such internal retry logic but I guess it was never considered as of yet.For now I'm going to put some sort of auto reboot mechanism into my homeassistant server which has a netgear integration that seems to have the ability to reboot a netgear router so I'll try; to implement some logic there to try at least 1 reboot if it ever gets into a similar state of loss of internet connectivity for > x minutes, try 1 reboot (maybe max 1 per day or something to stop it endlessly rebooting in cases where the internet is genuinely down).
But I think this has to be a very basic thing that has to be put into these routers to be honest, otherwise I can only see people lose faith in their robustness (even if in this case it was perhaps a 1 second blip in my actual internet providers connectivity).
If your seeing this across different FW versions with same ONT, this maybe a ONT or ONT to RBR interaction that may need to be looked at by the ONT Mfr. Orbi systems are meant and designed to be online 24/7 with out any user interventions for a reboot or power cycle. Uptime should be long weeks or months of being online with out problems. There been some posts on how long users have seen there routers be online with out issues. I've seen over 30days for some. We've seen some problems at the ISP equipment level when Orbi is connected. I see your ONT is fairly new and sports 10Gb speeds. Possible something in the connection here and the RBR that is not being handled well. The 750 series only supports 1Gb connection rates. Something to try, put in a non managed, non green ethernet 1Gb LAN switch in between the ONT and the RBR and see if the RBR continues to exhibit this issue. NGs GS105 or GS305 you should review and check on in between the ONT and RBR. Orbi systems should not need any form of reboot or power cycle to clear this condition, if so, then the cause needs to be investigated to the root cause point.
Thanks for your inputs. Is this something that, if common enough, the netgear team are able to try to reproduce on their end? I think it might be the best way to have these types of things handled, if the netgear engineers could themselves reproduce any such issues as I agree, a reboot isn't ideal.
For now I have put a homeassistant reboot workaround in but if netgear could reproduce any of these reported issues where users did have to perform workarounds, maybe some common root cause could be found?