NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Your experience with Firmware 2.2.1.210 released as of 10/3/18
The other long thread on the new firmware is useless and has become a tech support thread. Please only post your experience after upgrading to the new firmware, good or bad. I'd like to see everyone'...
Auto-Update, obviously.
Doesn't matter, been through 3 ISP vendors, same result.
3400 sq ft, 15 ft apart (1 floor).
Channel 1 & 48, Asus in barn on 11, no 5Ghz. No wifi neighbors (at least a quarter mile from any neighbor).
WPA2-PSK.
Trust me, no way I'm trying out Circle with Orbi's firmware record. :)
I've been through all of the 'offs' and 'ons' suggested previously. No difference except beam-forming on makes the restarts happen a couple of times daily.
I've lived in a heavy residential area, an apartment, and now a very, very rural area since getting Orbi. I honestly don't believe the location has anything to do with it's issues. All 3 environments have been unstable, except for that firmware they rushed out for the HomeKit issue. (2.1.4.16?) Of course auto-update ensured that was only a temporary reprieve. I will say I've always been in AP mode. Just looking for solid wifi, nothing more.
I'm not interested in starting from scratch, again. I'm not interested in continuation of being a test dummy for NG's firmware team. I'm only interested in being able to turn off auto-updates and choosing when I want my service interrupted or sticking to a firmware that works for my setup. And before you link to the Telnet options to turn it off, it doesn't work. Been there, done that.
Like I said, I'm hoping the finance committee gets tired of the issues and an alternative can be pursued.
usahale wrote:
Auto-Update, obviously.
Doesn't matter, been through 3 ISP vendors, same result.
ISP Modem kind does matter. Reason for asking as modem configuration is important. THis can be a cause as well.
3400 sq ft, 15 ft apart (1 floor).This is too close. Distance between Orbi base and satellites starts at 30 feet minimum. Too close causes problems.
Channel 1 & 48, Asus in barn on 11, no 5Ghz. No wifi neighbors (at least a quarter mile from any neighbor).
WPA2-PSK.
Trust me, no way I'm trying out Circle with Orbi's firmware record. :)
I've been through all of the 'offs' and 'ons' suggested previously. No difference except beam-forming on makes the restarts happen a couple of times daily.
I've lived in a heavy residential area, an apartment, and now a very, very rural area since getting Orbi. I honestly don't believe the location has anything to do with it's issues. All 3 environments have been unstable, except for that firmware they rushed out for the HomeKit issue. (2.1.4.16?) Of course auto-update ensured that was only a temporary reprieve. I will say I've always been in AP mode. Just looking for solid wifi, nothing more.
Others are reporing good operation with resets and setting up from scratch:
https://community.netgear.com/t5/Orbi/Your-experience-with-Firmware-2-2-1-210-released-as-of-10-3-18/m-p/1681722/highlight/true#M48325
https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-released-as-of-10-3-18/m-p/1647303/highlight/true#M42416
https://community.netgear.com/t5/Orbi/RBK40-Download-Speed-Slows-Down-After-5-Days/m-p/1643475/highlight/true#M41776
https://community.netgear.com/t5/Orbi/Orbi-MR-2-1-Update-3-23-18/m-p/1548414/highlight/true#M27868
https://community.netgear.com/t5/Orbi/speed-slows-down-Orbi/m-p/1551822/highlight/true#M28289
https://community.netgear.com/t5/Orbi/Is-2-1-3-4-in-auto-update/m-p/1553979/highlight/true#M28616
https://community.netgear.com/t5/Orbi/Orbi-Satellite-RBS50-Not-Connecting-via-Ethernet/m-p/1556692/highlight/false#M28949
https://community.netgear.com/t5/Orbi/Orbi-amp-the-new-Roomba-i7-connectivity/m-p/1655054/highlight/false#M44045
I'm not interested in starting from scratch, again. I'm not interested in continuation of being a test dummy for NG's firmware team. I'm only interested in being able to turn off auto-updates and choosing when I want my service interrupted or sticking to a firmware that works for my setup. And before you link to the Telnet options to turn it off, it doesn't work. Been there, done that.
Like I said, I'm hoping the finance committee gets tired of the issues and an alternative can be pursued.