NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
OrbiOS MR 2.1 issues
I wanted to reach out to provide a quick update on OrbiOS 2.1 software. We believe that these issues are affecting some users. Rest assured that we've been following this issue and working hard beh...
Do you think the customers are guinea pigs? Or we just have solid cash to throw $500 on junk products?
Why don't you learn a new concept called "Quality control and testing"?
The problem is not everybody is having issues with V2.1.2.18. For me it works fine. No reboots, no connection drops. Using 5Ghz wifi backhaul.
After reboot logs are wiped. Only settings survive. This can make it difficult to diagnose. Those users having problems must have enabled something that doesn't work well.
- I’m a brand new owner and highly disappointed with the connection drops. I’d like to assist in firmware testing if needed before I hit the “return to Costco” option. I’m an IT guy, but not a network specialist. I’m listening here for options.
What version of FW is currently loaded?
You can phone contact NG support and see if they have a beta available to use...
Try some of the following:
Disable Beamforming, MIMO, Daisy Chain or Fast Roaming if you have any of these features.
Orbi2018-3-3wrote:
I’m a brand new owner and highly disappointed with the connection drops. I’d like to assist in firmware testing if needed before I hit the “return to Costco” option. I’m an IT guy, but not a network specialist. I’m listening here for options.- My firmware is 2.0.1.4. I just wasn’t sure on how to get the beta versions because (probably for good reason) they aren’t typically available. I haven’t adjusted any settings so unless they options you mentioned are on by default they should be off. I’ll explore more.
wildhorsewrote:The problem is not everybody is having issues with V2.1.2.18. For me it works fine. No reboots, no connection drops. Using 5Ghz wifi backhaul.
After reboot logs are wiped. Only settings survive. This can make it difficult to diagnose. Those users having problems must have enabled something that doesn't work well.
It is curious why some people are having no problems with 2.1.2.18 and others cant even get an Orbi to work at all. Possibilities include:
- We don’t all have identical hardware, are all Orbi born the same ?
- Some systems have bad hardware, when good chips go bad
- Bit rot - devices that have been running a long time have bugs and/or resource leaks that eventually corrupt something
- We don’t all have the same environment, network components, cables, connectors, connecting devices, usage behavior. My favorite.
- People enabling telnet and buggering something up after logging into the Orbi
