NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR850 Frequent Disconnects Starting March 9th AM EST
Yesterday 3/9, starting at about 6AM EST, my Orbi system is disconnecting my Nest Cameras and Thermostat and my work laptop every 10-20 mins or so. I have about 20 devices connected to my mesh syste...
Reverting to 3.1.5.23 worked great until the device suddenly decided to update the firmware again. SMH!!!
Google to the rescue. I managed to find the instructions for telnet on a community forum here. For those of you who are interested:
To get back to 3.1.5.23 I had to do the following:
1) Log into the satellite's administration page directly (via the satellite's IP address) and click on firmware update. Load the 3.1.5.23 firmware version.
2) Log into the RBR (main unit) and click on Administration\Firmware update. Load the 3.1.5.23 version on the RBR (main unit).
3) Once everything has restarted, log into the main router's debug page (192.168.1.1/debug.htm) and click the enable Telnet button.
4) On a windows pc open a command prompt. Type telnet 192.168.1.1
5) Once a telnet session is established type:
5.1 nvram set auto_update_enable=0
5.2 nvram commit
5.3 exit
6) On the debug page disable telnet.
You will be on 3.1.5.23 and your Orbi will no longer automatically reach out for firmware updates.
Sorry, had to make one edit on my instructions in my previous post. The auto_update_enable should be auto_upgrade_enable. Revised instructions below.
To get back to 3.1.5.23 I had to do the following:
1) Log into the satellite's administration page directly (via the satellite's IP address) and click on firmware update. Load the 3.1.5.23 firmware version.
2) Log into the RBR (main unit) and click on Administration\Firmware update. Load the 3.1.5.23 version on the RBR (main unit).
3) Once everything has restarted, log into the main router's debug page (192.168.1.1/debug.htm) and click the enable Telnet button.
4) On a windows pc open a command prompt. Type telnet 192.168.1.1
5) Once a telnet session is established type:
5.1 nvram set auto_upgrade_enable=0
5.2 nvram commit
5.3 exit
6) On the debug page disable telnet.
You will be on 3.1.5.23 and your Orbi will no longer automatically reach out for firmware updates.
I just confirmed I am having the same issue as well. I had comcast come out since I noticed the problems since Monday (9th). Everything checked out and so I decided to try my old Asus Router I kept around as test. No more dropped connections. I looked to see if this was reported.
Now I will try to revert to the older firmware.Would be interesting to see if you loaded v3.2.9.2 after v3.1...
xnolightx wrote:Sorry, had to make one edit on my instructions in my previous post. The auto_update_enable should be auto_upgrade_enable. Revised instructions below.
To get back to 3.1.5.23 I had to do the following:
1) Log into the satellite's administration page directly (via the satellite's IP address) and click on firmware update. Load the 3.1.5.23 firmware version.
2) Log into the RBR (main unit) and click on Administration\Firmware update. Load the 3.1.5.23 version on the RBR (main unit).
3) Once everything has restarted, log into the main router's debug page (192.168.1.1/debug.htm) and click the enable Telnet button.
4) On a windows pc open a command prompt. Type telnet 192.168.1.1
5) Once a telnet session is established type:
5.1 nvram set auto_upgrade_enable=0
5.2 nvram commit
5.3 exit
6) On the debug page disable telnet.
You will be on 3.1.5.23 and your Orbi will no longer automatically reach out for firmware updates.
Let us know if reverting to v3.1 version gets your system stable again.
sprtxgy wrote:I just confirmed I am having the same issue as well. I had comcast come out since I noticed the problems since Monday (9th). Everything checked out and so I decided to try my old Asus Router I kept around as test. No more dropped connections. I looked to see if this was reported.
Now I will try to revert to the older firmware.
