NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
OrbiOS 2.1.1
The Orbi team at NETGEAR is aware that some users are experiencing higher than expected Orbi Router reboots, special characters in WiFi Passwords and WiFi / Internet disconnects. We believe these is...
Let me give you a quick update on where NETGEAR is with the OrbiOS.
Just before Christmas break, we paused the distribution of OrbiOS 2.1. Very soon, we're about to restart the distribution of a slightly updated version of the beta (2.1.2). In addition to the major new features introduced in 2.1 (e.g. Circle, Ethernet Backhaul), this firmware is expected to address the high CPU issue, as well as the special character in PSK issue as well as support for the Outdoor Orbi. Check Release Notes for complete list.
We are continuing to work on the issues with Google devices that have been documented in the press (several users have provided links here).
My recommendation is that you should either use the Orbi Mobile App (if you haven't seen it recently, check it out, we've made some major improvements) or the Web UI to check for new firmware or wait until your system gets auto-upgraded.
To answer your question, Stars_fan. When Orbi are connected over Ethernet backhaul, the 5GHz band becomes hot standby.
Orbi Product Management
aaz wrote:You might try the beta - I'm running it now and it's working well.
I don't know. I had no issues with 2.1.1.16 for 2 solid weeks (other than device reporting) and then it just died. No power spikes, surges, or anything. And I have it on a UPS anyway.
I could not get the web interface up or the debug page. Everything was dead. So after I piddled a while trying to fix it, called my ISP to check on network outages, connected my PC directly to the modem so I could get back online, and finally was dragging out my old gear to get my network back up, the Orbi came back to life.
That sounds more hardware than software, I'm thinking.
Right now I'm back on my old gear while I ponder my options.
What are the disadvantages of 1.11.0.20? .74 has been pretty stable bit even .74 resets wifi connections
Anyone already poked at the telnet access, which you can acticate on the debug page? I poked around a bit and found that, although the devices list is totally borked on my setup, the bridges pretty much tell me that the wireless devices are located on the device router/sat on which one would expect them to be.
I don't know, why the UI doesn't grasp that, but it seems to be only a minor issue, which should be easy to fix
I have put the two of my Orbi devices under tight surveillance by my network monitoring, should either of them fall of the net, it will be noted.
I finally fixed my problem with my orbi, very easy... I returned it to the store and got a velop linkys kit, this thing is rock solid. Good luck all
I have been having continued intermittent reboots over the last day or two since a manual update to V2.1.2.10
Orbi is in AP mode connected to an Asus router, also connected to the router is a Fingbox.
The Fing is reporting the Orbi having a MAC ending XX:XX:A5 and being connected to the network with no problems.
Then Fing then reports the Orbi as being "in range" and the network seems to degrade.
Followed by Left the network.
Shortly after it re enters the network.
But, at the same time, R50 enters the network on the same IP but with MAC XX:XX:A6 (only the last digit differs)
Both MAC's then leave the network and the Orbi setup crashes/reboots.
The timeline might not be exact and am unsure how accurate the Fingbox is.
I am trying to work out why the Orbi would be connecting with the MAC variation - changing from A5 to A6 ? or is this considered acceptable from a device with multiple MAC's
Certainly if the reboots continue I will revert to .74
