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 issues are related to the OrbiOS 2.1.1 firmware. We are actively working to address these issues, and expect to fix them with a firmware upgrade soon. In the meantime, we’re temporarily suspending auto-upgrading users to OrbiOS 2.1.1.
While we work through some of the issues, we’re releasing a new Beta firmware (2.1.2), which contains:
- Support for LED control & scheduling for Orbi Outdoor Satellite (RBS50Y)
- Fixes high CPU utilization on Orbi Router, which could be causing other issues
- Fixes the Attached Devices UI showing all devices connecting to the Orbi Router
The Beta firmware 2.1.2 files can be obtained from here:
RBR50: http://files.netgear-support.com/go/?a=d&i=n2X2ARvI7o
RBS50: http://files.netgear-support.com/go/?a=d&i=yBsnhHaBiw
RBR40: http://files.netgear-support.com/go/?a=d&i=8xFS1yg8fn
RBS40: http://files.netgear-support.com/go/?a=d&i=Hu3hbx814i
RBW30: http://files.netgear-support.com/go/?a=d&i=PRpkMfJynw
RBS20: http://files.netgear-support.com/go/?a=d&i=OGhLlDB9mQ
Instructions for performing a Manual Upgrade: https://kb.netgear.com/000037217/How-do-I-check-and-manually-upgrade-the-firmware-on-my-Orbi-satellite
If you are having issues with 2.1.1, having higher than normal disconnects or if you have purchased an Outdoor Orbi Satellite (RBS50Y) please upgrade to the new Beta firmware through the manual upgrade process. Feel free contact NETGEAR Support if you’re having issues with MR 2.1.1 (even if you’re outside of the 90 day window).
We apologize for these issues.
Orbi Product Team
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
371 Replies
Replies have been turned off for this discussion
Updated to 2.1.2.18, so far things seem OK but I find this a bit funny.
The router believes my 3D Printer is connected to the Satellite but in some unknown way? (it's wireless btw). The Satellite doesn't see it connected at all....
Is the expected behavior for a wired backhaul to disable the satellite radio? If I unplug the cable 5G connects and enables the satelites radio again.
I'm not having any of the reboot issues. The only android in my house is my A1E Sony TV but that's wired.
Also having a $ in your SSID password is not fixed in the beta.
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
AmitR wrote: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
AmitR Very much appreciate the update. I do want to try and understand one thing...
The Release notes for 2.1.2.16 lists:
Bug Fixes:
- Fixes the issue where connected devices do not display on the Attached Devices page.
- Fixes the issue where connected devices on the Attached Devices page do not displays the correct Orbi that they’re connected to.
- Fixes the issue where the CPU usage is high when the Orbi in AP mode.
The release notes for 2.1.2.18 lists:
Bug Fixes:
- Fixes an issue which causes high CPU on Orbi routers.
- Fixes the issue where the attached devices do not display correctly on the Attached Devices page.
- Fixes a WiFi issue if the WiFi password contains special characters,
- Fixes the issue where the satellite sometimes are shown as disconnected on Attached Devices Page.
Have the other "fixes" been updated as well? I don't have any special characters in my password. Should I expect ANY difference on this Firmware if I already updated to beta 2.1.2.10?
Thanks.
Stars_fan wrote:Also having a $ in your SSID password is not fixed in the beta.
I have a beta that fixes the $ in password issue. For some reason they have not put it out to a wider beta but it has been stable for me for about a week. I don't think it fixes the Android issue and as I said before it's likely anyone that had a $ in their password removed it by now so that is not as big an issue. Still if you want that try PM the moderators.
- Or just go back to 1.11.0.20. Orbi Pro is running a 1.x firmware if I'm correct.
My Orbi is on day 3 of uptime since downgrading and power cycle of my modem, switch and orbis. I have Google homes, Chromecast and Android 8.1. No issues. I have similar issues like other unhappy customers on this forum. Purchased RBK50 system (Router RBR50 + 1 Satellite RBS50)
Have about 40 devices on my network, some of them are Android.
After upgrading firmware to 2.1.16 I had constant router reboots. I tried pretty much everything recommended by other users:
1. Upgraded firmware to 2.1.2.10 Beta (Satellite first, then router - as recommended)
2. Tried Enabling/Disabling: UPnP, Beamforming, MU-MIMO, FastRoaming (presently still ALL disabled)
3. Disabled Daisy-Chain Topology (don't really needed as I only have 1 satellite but it was enabled by default)
4. I do NOT use wired ethernet backhoul to connect main router to satellite
5. Did factory reset on both (router + satellite), then another clean upgrade to 2.1.2.10
6. Changed my SSID upon factory reset
7. Changed WIFI channels and location of the router+satellite to avoid potential interference with other devices on the network
None of these things helped and I still have daily reboots.
So I finally called Netgear support and spent about 2 hours today (most of it being on hold), before they suggested to replace my Orbi router due to potential hardware defect.
I also provided debug logs (that were captured just minutes after another crash this morning) but they were not interested in analyzing logs or escalating to the next level of support (which is L2 I believe)
It is very unlikely that this is hardware related problem but they were willing to replace my router before investigating further.
I had to pay about $25 CAD for Advanced RMA return process in order to receive new unit before shipping the old/deffective one.
It's free only if you send them your deffective product first and then wait for replacement, which was not an option for me becuase I no longer have my old router.
- I went through the support and replace process with two satellites. They satellites they sent had really old firmware (1.4.x), and couldn't be updated easily. I had to jump through a lot of hoops nerwork-wise to get them upgraded, and even then I still had the same problems. All in all it was a waste of several hours.
My problem isn't reboots, though - it's just loss of internet connectivity through the satellites. Local connections continue to work.Yes, I have a feeling that replacing my router is going to be a total waste of time and money. I'm still suprised that support guys did not want to analyze my router debug logs and try to figure out what the problem is. It may be cheaper for them just to send new unit...
It is also interesing that hey only wanted to replace my router and not the satellite that comes in the RBK50 package.
When i pointed out that my replacement router will likely have a different firmware than my satellite and cause another firmware upgrade etc. , they offered a free satellite exchange if it turns out that the problem is not related to my router. Bizare.
Another unhappy user:
- Tested with latest realease and with latest beta, same results
- Router does not reboot very often but wifi stops working ever few hours for few seconds to minutes (even on windows laptops)
- Wired backhaul seems to make it worse - more frequent disconects
- Router will lockup and reboot as soon as satalite is connected to wired network
- Have to turn of the Satalite, let router come up and then power on the satalite
- Have a large number of Android devices, including Google home and Chromecast
- Same defivices worked fine on Cisco router + Netgear Nighthawks in AP mode
2.1.2.10 seems to be fine in my setup with 1 Pixel2, 2 Google Homes and 2 Chromecasts but only when running without the satellite. As soon as I turn the satellite on, the router reboots as soon as I wake my phone. I've noticed that when actually casting content to anything (Homes or Chromecasts) there are periodic wifi drops when I wake the phone, but the router at least stays up.
As an aside, the Cisco AIR-CAP1700's I run at work in an 8 point mesh with a Cisco WLC2100 central controller also have issues when there are several of our Pixel/Pixel 2 devices in the office. I have also received alerts from our IPS that there is a potential DoS attack coming from the devices after long sleep times. Google really needs to address this instead of passing it over to the other hardware manufacturers.
Well google does have an issue with there devices, but so does Netgear.
For example:
- connecting the Satalite via wired ethernet cause the Router to reboot (thats a pure Netgear problem).
- Windows laptop wifi connection losses access to external (internet sites). Can ping the router, the router can ping internet sites but laptop cannot ping internet sites. This is happens on Windows and Mac Laptops. Disconnecting and reconnecting the Wifi fixes the problem. This is clearly a routing issue with the router (not the satalite).
Have tried doing a factory reset on the router and the satalites (have 2 of them). Lets see if there is a firmware update to fix this in a week otherwise will have to abadon Netgear for good.
A bit of irony here on my side maybe karma came and got me after my earlier post. My satellite went an locked up this evening (purple ring). Power cycled it and it came back up and all is good again. Orbi router was and still is fine though. Probably not related to FW issues since symptoms are completely different but who knows...
- And oddly enough after 8+ days running, my router spontaneously rebooted when I apparently roamed my Android 7.0 S7 from Satelitte to Router.
- I had issues even with the beta. I've rolled back to 1.x acted having issues with .74. Admittedly I did not fully power cycle my whole system when I rolled back to .74 although I don't think that was the cause of the reboots. However I was having issues where my device would show connected no internet.
Anyhow there is now peace in my family with the following changes I made. Should not have to do this with orbi though.
I'm not sure if only one of these was an issue or cumulative effect.
Telnet disable auto update
Rollback router and satellite to 1.11.0 .20
Reset nvram
Reset router and satellite to default with Paperclip then turn off and unplug
Turn off cable modem and switch and unplug
Wait a minute or two
Turn modem and switch back on
Turn satellite and router back on
Setup as new system
I used my original network name and password so my devices would reconnect without reconfiguring. This was a big deal because I have bows and ring doorbell and those are a process to entered WiFi username and passwords
My system has been up over 24 hours with 0 reboots. Additionally I can tell that the Wi-Fi connections to my devices have not been dropped.
For the time being I will stick with this firmware. It meets my needs. I reckon I'm slightly vulnerable to the krack exploit
I will monitor this forum to see when a working firmware update comes outFWIW I have Android 8.1 (Pixel XL2), 2 google home and a chromecast on 1.11.0 .20 with no current issues. My perception is if Android OS and home devices are causing issues it's still related to 2.x firmware
I have two Satllite Orbi devises connected to this router. I had no issues for several months purchased in early March 2017 up until October 2017 everything worked great. Now I have Internet disconnects almost every hour through out the day 24/7. Started out as once or twice per day and has continued to get worse. I opened a trouble ticket over a month ago have gone to support directly three times. We have made several changes to setup and done Firmware updates.Current Firmware version is 2.1.1.16. I read there is a Beta software out that is Supposed to fix this issue Can anyone confirm?
I know how to do Firmware updates manually please send me the Firmware update link for this Beta version if it is correcting the issues. Extrmely frustrating issues. Very expensive devises to have issues like this is frustrating. Everything else about the product is fantastic and I loved it for several months. I even purchased for one of our sons at his home so far he is fine. But I am affrad that will change after a few more months. Please advise.
Since I don't have any immediate issues to address for now I'm going to wait until 2.1.2 is finalized an officially released to install.
FWIW I've been running on 2.1.1.16 since whenever it auto updated last without any issues. CPU Usage is < 10% and uptime is currently 24 days. I am looking forward to the attached devices page showing the correct connection bug getting fixed though. We have very few android devices on out network (an older Acer tablet, and an Acer chromebook). Everything else is Windows, Apple, or an IOT device. Have had a some freqent random disconnects with only 2 (my wife's iphone 6 and ipad 2) of the half dozen Apple devices. Other than that have not noticed any other issues with the current FW version.
Have yet to see an accurate representation of what is actually connected to the RBKS on the latest firmware release.
