NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WARNING: Firmware 2.2.1.210 is junk
If you're dealing with poor WiFi performance, frequent disconnects and so on, you aren't alone, there are various other threads on this topic. Here's what you need to know:
Check if your Orbi...
Hi UnhappyOrbiUser
I'm having troubles with router constantly going offline (modem stays online rock solid as confirmed by conecting directly to modem, it is just the router for whatever reason decides it is offline all of a sudden). The only fix is to restart the router. This is on f/w 2.2.1.210 so I thought I'd try going back to 2.1.4.16 to see if it is any better.
Now I followed your and DUSTOFF2 instructions and while everything worked as described and I managed to easily install 2.1.4.16, the issue is that it automatically updated back to latest 2.2.1.210 in no time. It looks like it is not enough to zero nvram orbi_auto_upgrade, auto_check_for_upgrade and auto_update settings to diable auto-update. It will still auto-update to latest firmware regardless.
I'm puzzled how did this work for you on 2.2.1.210. These don't look to suppress auto-update. Any ideas please?
Thanks
Some users have posted about either doing a factory reset and setup from scratch after the autoupdate completes or manually loading v210 FW files first, then factory reset and setup from scratch. This has solved many users problems.
vcuser1 wrote:
Hi UnhappyOrbiUser
I'm having troubles with router constantly going offline (modem stays online rock solid as confirmed by conecting directly to modem, it is just the router for whatever reason decides it is offline all of a sudden). The only fix is to restart the router. This is on f/w 2.2.1.210 so I thought I'd try going back to 2.1.4.16 to see if it is any better.
Now I followed your and DUSTOFF2 instructions and while everything worked as described and I managed to easily install 2.1.4.16, the issue is that it automatically updated back to latest 2.2.1.210 in no time. It looks like it is not enough to zero nvram orbi_auto_upgrade, auto_check_for_upgrade and auto_update settings to diable auto-update. It will still auto-update to latest firmware regardless.
I'm puzzled how did this work for you on 2.2.1.210. These don't look to suppress auto-update. Any ideas please?
Thanks
Thanks. Think I figured it out. Reading through the whole unfiltered dump of 'nvram show' I found another setting 'orbi_auto_upg=1' (note the missing suffix in the name). Switching this to 0 did te trick. I'm not sure whether 'orbi_auto_upgrade' is something else or was created by me when I followed Butche's instructions where he has it as 'orbi_auto_upgrade' rather than 'orbi_auto_upg'.
Anyways, setting 'orbi_auto_upg=0' prevented it from auto-updating and now it shows f/w update button in the html admin portal and in Orbi apps telling there is newer f/w but not automatically installing it.
I'll see how 2.1.4.16 compares to 2.2.1.210 in the long run.
Some users have posted about either doing a factory reset and setup from scratch after the autoupdate completes or manually loading v210 FW files first, then factory reset and setup from scratch. This has solved many users problems. Something to try upon next upgrade.
vcuser1 wrote:
Thanks. Think I figured it out. Reading through the whole unfiltered dump of 'nvram show' I found another setting 'orbi_auto_upg=1' (note the missing suffix in the name). Switching this to 0 did te trick. I'm not sure whether 'orbi_auto_upgrade' is something else or was created by me when I followed Butche's instructions where he has it as 'orbi_auto_upgrade' rather than 'orbi_auto_upg'.
Anyways, setting 'orbi_auto_upg=0' prevented it from auto-updating and now it shows f/w update button in the html admin portal and in Orbi apps telling there is newer f/w but not automatically installing it.
I'll see how 2.1.4.16 compares to 2.2.1.210 in the long run.
- FYI I have a RBR20 and one RBS20 network that worked great for about a week. Then the reported drop outs started. I’ve tried pretty much all the workarounds with no real difference. Even unplugged the satellite for awhile. Realized that a firmware update was probably the only real fix. Waited several months and today I found and had to manually download and install 2.3.0.28 (didn’t show up in the admin GUI for available firmware updates ) and it seems like it’s working okay. Time will tell and I’ll report back one way or another. Thanks everyone for the data collection!