NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR50 power LED blinking green, now appears hung or dead
So in the middle of my Teams meeting this morning my network just disappeared. I did the normal fault searching, and concluded the fiber-optic connection to my ISP is fine, the issue is with my RBR5...
Mstrbig wrote:If you rebooted the ONT before connecting the Orbi, then connected the Orbi router from a LAN port on the ONT to the WAN port on the Orbi, then turned on the Orbi and ran the Orbi setup, and you have no lights on the ONT LAN, You pretty much proved it is possibly dead.
I tried powering everything off and connecting and turning on components in different orders, no change.
Then I tried this:
https://kb.netgear.com/000059633/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP-client
During preboot I could actually ping 192.168.1.1, and the tftp upload completed on the first try.
I got my hopes up, but then thought it was still a failure as switching the laptop back to DHCP and waiting for the router reboot to complete I could no longer ping 192.168.1.1 and attempting to access http://192.168.1.1/ with a browser timed out.
I was about to shut it all down again when I noticed one of my wifi camera indicator lights go green. It had connected to a network that should not have been available. I double-checked the Ethernet properties on the laptop in front of me, and it had indeed received a 10.0.1.* address.
Turns out none of the many factory reset attempts had erased my configuration, so when I rebooted with firmware V2.5.1.16 it happily picked up where it left off, with the same wifi SSID and IP range which I had changed from the default to 10.0.*.*.
Only difference is I am now running V2.5.1.16 (which is what I uploaded manually through tftp) instead of V2.3.5.30, which I have avoided upgrading from since it has been so stable for me.
My assumption is that the router decided to force an automatic firmware upgrade on me in the middle of my Teams call, despite my manual cancellation of the upgrade all these months. It botched the upgrade leaving the router bricked.
If you rebooted the ONT before connecting the Orbi, then connected the Orbi router from a LAN port on the ONT to the WAN port on the Orbi, then turned on the Orbi and ran the Orbi setup, and you have no lights on the ONT LAN, You pretty much proved it is possibly dead.
Mstrbig wrote:If you rebooted the ONT before connecting the Orbi, then connected the Orbi router from a LAN port on the ONT to the WAN port on the Orbi, then turned on the Orbi and ran the Orbi setup, and you have no lights on the ONT LAN, You pretty much proved it is possibly dead.
I tried powering everything off and connecting and turning on components in different orders, no change.
Then I tried this:
https://kb.netgear.com/000059633/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP-client
During preboot I could actually ping 192.168.1.1, and the tftp upload completed on the first try.
I got my hopes up, but then thought it was still a failure as switching the laptop back to DHCP and waiting for the router reboot to complete I could no longer ping 192.168.1.1 and attempting to access http://192.168.1.1/ with a browser timed out.
I was about to shut it all down again when I noticed one of my wifi camera indicator lights go green. It had connected to a network that should not have been available. I double-checked the Ethernet properties on the laptop in front of me, and it had indeed received a 10.0.1.* address.
Turns out none of the many factory reset attempts had erased my configuration, so when I rebooted with firmware V2.5.1.16 it happily picked up where it left off, with the same wifi SSID and IP range which I had changed from the default to 10.0.*.*.
Only difference is I am now running V2.5.1.16 (which is what I uploaded manually through tftp) instead of V2.3.5.30, which I have avoided upgrading from since it has been so stable for me.
My assumption is that the router decided to force an automatic firmware upgrade on me in the middle of my Teams call, despite my manual cancellation of the upgrade all these months. It botched the upgrade leaving the router bricked.