RBR850 Frequent Disconnects Starting March 9th AM EST

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.

 

---

Just an FYI for anyone who's downgrading their firmware: the Orbi will auto-update itself unless you stop it from doing so.  This happened to me, though seemingly my network is more stable now (I did a factory reset and downgrade, then was automatically re-upgraded).  For whatever reason, things seem more stable on my network since going through the downgrade, reset, and upgrade process.  I'm keeping an eye on it though.

So are you back on v10.11? 

If you are, be sure to check your CTS and RTS values. If they are at 64, please change both to 2347.

---

d1mmy wrote:

Just an FYI for anyone who's downgrading their firmware: the Orbi will auto-update itself unless you stop it from doing so.  This happened to me, though seemingly my network is more stable now (I did a factory reset and downgrade, then was automatically re-upgraded).  For whatever reason, things seem more stable on my network since going through the downgrade, reset, and upgrade process.  I'm keeping an eye on it though.

 

---

Is there no way to turn off auto update?  

---

FURRYe38 wrote:

So are you back on v10.11? 

If you are, be sure to check your CTS and RTS values. If they are at 64, please change both to 2347.

---

d1mmy wrote:

Just an FYI for anyone who's downgrading their firmware: the Orbi will auto-update itself unless you stop it from doing so.  This happened to me, though seemingly my network is more stable now (I did a factory reset and downgrade, then was automatically re-upgraded).  For whatever reason, things seem more stable on my network since going through the downgrade, reset, and upgrade process.  I'm keeping an eye on it though.

 

---

 

---

Yes, I'm back on 3.2.10.11 and it set me back to CTS/RTS defaults of 64.  I'll bump it up as a first next step if I encounter additional connectivity issues.  My problems could have been resolved by the factory reset (for all you other folks out there...it's a PITA, but might work).

---

DBV wrote:

Is there no way to turn off auto update?  

---

xnolightx included instructions on how to disable auto-update:

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.

DBV I provided instructions earlier for this:

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.

Thanks - all I have is Mac's.  Is there a way to do that their too?

I use this for OSX:

https://emtec.com/download.html

---

DBV wrote:

Thanks - all I have is Mac's.  Is there a way to do that their too?

---

---

DBV wrote:

Thanks - all I have is Mac's.  Is there a way to do that their too?

---

This may help: https://www.wikihow.com/Use-Telnet-on-Mac-OS-X

I am experiencing the same issue. Been using the router since December. No issues until now.

Have called support 4 times. Have sent logs of the disconnects to my support case. Still no resolution. Had to switch back to my old TP link router while Netgear tries to find a fix for the random frequent drops. Have been advised they cannot provide refunds even though the product is under warranty. 

From my support case:
Was able to verify registered account information? Yes - updated profile =========== Technical History and Information ============ - Is the customer aware of the NG or Orbi app? Yes If not, did you promote the app to the customer? If not, why? ISP: Frontier Modem: ONT box Firmware: V3.2.9.2 Received call from Orbi AX - 4:45 AM 3/11/2020 - internet keeps on disconnecting every 20 minutes - asked if affect all devices at the same time; he said yes - asked if wired devices are affected; he's not sure - wireless devices stays connected; internet will reconnect right real quick - customer already reset the router 4 times today - called ISP; they check the ONT box and said everything is working fine ============ Troubleshooting Details ============== - accessed web ui; yes FW: V3.2.10.11_1.2.12 - downgraded the firmware of the satellite and the router to V3.2.9.2 - power cycled both units - advised to observe the connection - check if issue affects wired devices and if it does check the connection straight from the ONT box ============== Resolution Summary =============== - for observation =============================================== Attached/Sent KB Article? Yes Promoted Support Site? Yes Mentioned Survey Spiel? n/a Provided Case Number?yes Pitched for PS/GH? n/a

So far we have downgraded firmware to V3.2.9.2 - still drops
Hard reboot (x3) - still drops
Changed CTS and RTS values to 2347 - still drops
Changed wifi channels to 44 - still drops
re-upgraded back to V3.2.10.11_1.2.12 - still drops
Hard reboot #4 - still drops

I am on day 4 of interuption and all NG says is that they are "working on it". I wasn't informed until my call with support today that this is a known issue. Upset that I have spent over 10 hours the past 4 days troubleshooting the router thinking this was an isolated issue. For a $700 router, this is unacceptable.

I just downgraded to V3.1.5.23 and disabled auto firmware upgrades.

We'll see if this helps.

---

cruisencode wrote:

I just downgraded to V3.1.5.23 and disabled auto firmware upgrades.

 

We'll see if this helps.

---

Well, I guess I didn't do something correctly when disabling auto firmware upgrades.  My router and satellite were upgraded to V3.2.9.2 last night.  I'll see how it goes before trying to downgrade again.

OK, I'm not sure why the new firmware was installed.  I just checked through telnet and auto_upgrade_enable is set to 0.

root@RBR850:/# nvram get auto_upgrade_enable
0
root@RBR850:/# nvram get auto_update_enable
0

---

cruisencode wrote:

---

cruisencode wrote:

I just downgraded to V3.1.5.23 and disabled auto firmware upgrades.

 

We'll see if this helps.

---

Well, I guess I didn't do something correctly when disabling auto firmware upgrades.  My router and satellite were upgraded to V3.2.9.2 last night.  I'll see how it goes before trying to downgrade again.

---

And, the issue is back.  Time to downgrade again.  Sigh...

Netgear should have fixed this already.  Can't they put out a new firmware that is essentially the last firmware that works and also there should be a check box that enables you to do manual downloads.  I should not have to figure out how to go in some other way and program it.  

Most people that buy this stuff are not that technical.  This is ridiculous that is had gone this long and especially now when most people work from home.  Who has time to fumble through all these steps that may or may not work?

Netgear get something done and sent out today and please add an option in the future to manual upgrade.  Every other software I have ever seen has that.   This router cost big money and expect perfection!

---

cruisencode wrote:

---

cruisencode wrote:

---

cruisencode wrote:

I just downgraded to V3.1.5.23 and disabled auto firmware upgrades.

 

We'll see if this helps.

---

Well, I guess I didn't do something correctly when disabling auto firmware upgrades.  My router and satellite were upgraded to V3.2.9.2 last night.  I'll see how it goes before trying to downgrade again.

---

And, the issue is back.  Time to downgrade again.  Sigh...

 

cruisencode I also had an auto update last night even though I set the values via telnet. I'm wondering if it requires a reboot, which I will try today after downgrading and setting the value again.

---

Just a question. Why on earth would Netgear roll the latest version available back to 3.2.9.2 when they know people are also having problems with that version as well.

The community has confirmed for them that 3.1.5.23 works. This is just madness. If I had bought this device from Amazon I would be sending it back now. 

There isn't a problem with v3.2.9.2. Only something with v10.11 after getting pushed from the auto update servers does something break then also breaks v3.2.9.2 even after users downgrade to that version. v3.2.9.2 was working before v10.11 came to the picture. Someone else just said that they downgraded then let the system upgrade again to v10.11 and now there system is stable again. 

NGs Auto push update servers have had a long history of causing problems for Orbi AC. This maybe still the case with Orbi AX. 

Lets give NG the change to fix this. Again, something in the auto update servers or something happened in the push that causes problems. Those of us who got this update before the push have not seen any issues as seen with those of you who got pushed too, aside the CTS and RTS values being changed. Even then the system worked for us. Let be patent while NG works on this. 

In mean time users can downgrade to v3.1 or or use there Orbi AX in AP mode with there prior router until NG comes out with something. 

---

xnolightx wrote:

Just a question. Why on earth would Netgear roll the latest version available back to 3.2.9.2 when they know people are also having problems with that version as well.

 

The community has confirmed for them that 3.1.5.23 works. This is just madness. If I had bought this device from Amazon I would be sending it back now. 

---

Takes time to review and test and reproduce. Maybe something they can't as well. Some of us who got this same version haven't seen problems. We've considered this one of the better versions to date. It may not be something in FW rather NGs auto update push services that maybe causing problems. We got this via same services however it wasn't auto pushed. It was available to manually installed from the services. We can to start the install process. After that we factory reset and setup from scratch and has been stable for us since. Though we see that the CTS and RTS values were changed which may cause wifi problems. Changing them back to 2347 is recommended. My system is stable and remains that way after the change. 

Making changes if FW doesn't happen over night. Please be patient. 

Ether downgrade to v3.1 or put your prior router on line and configure the RBR for AP mode while NG works on this. Either one of these methods should keep you up and running in mean time. 

---

DBV wrote:

Netgear should have fixed this already.  Can't they put out a new firmware that is essentially the last firmware that works and also there should be a check box that enables you to do manual downloads.  I should not have to figure out how to go in some other way and program it.  

 

Most people that buy this stuff are not that technical.  This is ridiculous that is had gone this long and especially now when most people work from home.  Who has time to fumble through all these steps that may or may not work?

 

Netgear get something done and sent out today and please add an option in the future to manual upgrade.  Every other software I have ever seen has that.   This router cost big money and expect perfection!

---

Did your system re-update to v10.11 when you had v3.2.9.2 loaded? 

Did you input nvram commit after making the changed in telnet? 

---

cruisencode wrote:

---

cruisencode wrote:

---

cruisencode wrote:

I just downgraded to V3.1.5.23 and disabled auto firmware upgrades.

 

We'll see if this helps.

---

Well, I guess I didn't do something correctly when disabling auto firmware upgrades.  My router and satellite were upgraded to V3.2.9.2 last night.  I'll see how it goes before trying to downgrade again.

---

And, the issue is back.  Time to downgrade again.  Sigh...

---