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 behind the scenes to address it. In the meantime, to those that are affected, I understand the frustration that you've been feeling. In response, we're taking the following actions:
1. We've paused the auto-firmware upgrade to MR2.1 and are re-posting MR 2.0 as the "latest" software for Orbi. What that means is that new customers will, upon first install, get upgraded to OrbiOS 2.0. They will not be able to use features introduced in OrbiOS 2.1 like Ethernet Backhaul or Circle. This will happen in the next 24 hours. Existing customers, can do a manual software upgrade back to MR 2.0 and it will stick until further notice.
For those interested in OrbiOS 2.1 features, We will post OrbiOS 2.1 available on the web server for customers who want to manual upgrade.
2. Customers who are having connectivity issues on MR 2.1 are encouraged to contact Support. We will try to help everyone. Bonus points if you're willing to work with us. We have some debug software available.
3. As more information is available, we'll keep you updated through the Community.
As an FYI, if you're having issues, a couple of quick & easy ways to self serve
1. Ensure that your Router & Satellite(s) are running the same (to the 3rd digit) of software. Best way to find this is on the Web UI (orbilogin.com. Advanced -> Admin -> Firmware Update).
2. Rebooting the system. Do this manually by unplugging & replugging in the Router & Satellites.
3. If you're having slowness when connected to the Satellite, moving it closer to the Router or to a different location
Orbi Product Management Team
140 Replies
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.
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
I've been running 2.1 now for a few months. Initially using mesh caused nothing but problems. Once I switched to hub/spoke it's now working amazing and I'm using it heavily. I'm streaming full native 4k blu-ray video over wireless with the devices plugged into the lan ports (nvidia shields) and I never have a hiccup. That's pretty great considering you really need a full wired connection normally for that.
AND I'm running THREE satellites in my system, btw.
it's an amazing system if you set it up correctly. Not perfect though.
I am also having issues with 2.1.
- I have 2 satelites and 1 router.
- I have xfinity 130 down and 20 up.
- 32 connected devices (mostly apple and home automation)
All the metrics look good, but periodically throughout the day I loose internet/connectivity. I have also noticed with 2.1 when adding any real load to traffic, everything conected suffers. I am not talking about slower speeds, I am talking about everything stops. For example, pushing a 600mb docker image to google cripples my wireless network. The push happens from a wired connection that is plugged into the RBR50. Any help or testing I am can do I am willing.
I am loosing my faith in this setup, but not ready to throw in the towel.
Thanks
7b7wrote:I am also having issues with 2.1.
- I have 2 satelites and 1 router.
- I have xfinity 130 down and 20 up.
- 32 connected devices (mostly apple and home automation)
All the metrics look good, but periodically throughout the day I loose internet/connectivity. I have also noticed with 2.1 when adding any real load to traffic, everything conected suffers. I am not talking about slower speeds, I am talking about everything stops. For example, pushing a 600mb docker image to google cripples my wireless network. The push happens from a wired connection that is plugged into the RBR50. Any help or testing I am can do I am willing.
I am loosing my faith in this setup, but not ready to throw in the towel.
Thanks
The fact that Netgear has pulled the 2.1 release and is holding new customers at 2.0 tells me that they have no faith in that release. I would roll back to what Netgear thinks is a stable release assuming you are not married to the ethernet backhaul.
https://www.netgear.com/support/product/RBK50.aspx#download
I contacted support after seeing this message
AmitRwrote:2. Customers who are having connectivity issues on MR 2.1 are encouraged to contact Support. We will try to help everyone. Bonus points if you're willing to work with us. We have some debug software available.
I contacted support and their "help" was to tell me to downgrade the firmware; no attempt to troubleshoot or mention of debugging tools. \"We have the latest firmware which is 2.0.1.4 at the moment. Yes, it is a downgraded firmware with the fix since we are currently having issues with our 2.1 firmware versions.
Update the firmware then observe the connection of the Orbi with this firmware. "Currently have no issues, running V2.1.2.18.
I have a very simple setup though. RBK50 and 2 RBS50's. No guest network. NAS connected to router. 10 Devices (including 3 ip cam's)
(
getting average lan speed (connected to (wireless)sat-(wireless)router-wiredNAS) though: 170 Mbps write / 230 Mbps read. Laptop sitting 2 meters from Sat, connected to 5Ghz. But good enough for me.
)
- It would help if the support team would address and give instructions for daisy chaining satellites. I know the firmware update allows this, but I don't see it anywhere. Every issue I see regarding satellites is that they should be positioned close to the router; thus not benefitting from purchasing additional satellites if they can't be close to the router... If my router sees my added satellite, and links to it without daisy chaining then I'll get a weaker signal than if it was linking to the sattletite that is actually closer. I want daisy connection, not star.
Nothing, I have Daisy chain running on my second Sat. Connect Sat to Router and put it where you want it to be. I'll connect automatically to your other Sat.
bramddwrote:Nothing, I have Daisy chain running on my second Sat. Connect Sat to Router and put it where you want it to be. I'll connect automatically to your other Sat.
If I am still at 2.0.0.56, I suppose daisy chain function would not be available? This is what I really need as my iMac is located in the study room many walls from the router. It needs another satellite to bridge the cover.
How to download firmware MR 2.1 ?
quentinwrote:How to download firmware MR 2.1 ?
Netgear,
Can you guys please add a button in the UI to disable the auto firmware upgrade? Or give direction on how to permanently disable it through telnet.
Can anyone confirm if the current 2.0 firmware doesn't break with a special character in the psk?
I've noticed the wireless speeds (time machine, plex & all internal connections) seem to be slower on 2.1
After 6 hours yesterday of factory resets and testing I can state without a fact that a password of ALL numbers will break your security/DHCP server.
I downgraded my firmware to 2.0.1.4 and forgot to change the password. When I went in to set it to our "standard" password of all numbers I immediately had an issue connecting again. Over the next couple of hours I went through several factory resets and the end result was the same.
Finally, I performed a factory reset and left the ORBI SSID and PASSWORD. The unit was stable for an hour so I logged in and changed the SSID to our SSID leaving the default ORBI password. The unit was stable for an hour so I then logged in and changed the password to an 8 number one. Immediately I had issues. I connected to the router with an ethernet cable and the DHCP server had issues assigning me an IP. After approximately 5 minutes I received one and changed the PASSWORD to a mix of alpha numeric characters. It started working when it updated the router and propogated to the satellite.
It has now been 12 hours with no issues of connecting, no drops, and no speed issues. I now have to go around and update 50+ devices (cameras, remotes, tablets, thermostats, etc) today.
Hope this helps someone else not waste hours and hours chasing an issue that should not be there. This was not an issue in 2.2.18.
JC
I have a special character in my new password and it is working fine on 2.0.1.4
I am having this problem and it is driving me nuts! I have recommended the Orbi system to so many people and despite a rocky start with poor firmware testing, it has been rock solid for a good 6 months or more. But now, my devices a dropping constantly. Your post says contact support for a solution - can I have that please because my network is currently operating at 20%.
Thanks
- This thread mentioned Firmware 2.1.1.18 and what I found yesterday was 2.1.1.16; does this mean that Netgear feels that this"prior version" is more stable than the 2.1.1.18?
bardiferouslywrote:
This thread mentioned Firmware 2.1.1.18 and what I found yesterday was 2.1.1.16; does this mean that Netgear feels that this"prior version" is more stable than the 2.1.1.18?Maybe a lot of typos by people here, but to be clear on version numbers:
* 2.1.1.16 - Late December autoupdate release. Lots of problems. Pulled by Netgear before Christmas.
2.1.2.18 - January autoupdate release. Better but lots of problems for some. Pulled by Netgear a week or so ago.
2.0.1.4 - Current "best" release for autoupdates. Seemingly similar to 2.0.0.74, but may include the Krack fix and a fix for memory leak on satellites.
Yes. Netgear is effectively saying the 2.0.1.4 version is currently their best release.
FWIW, 2.0.1.4 seems better than the others I've tried thus far.
I would recommend to downgrade only if you have issues with the latest. Older version could have other problems.
Its a pitty Netgear don't release firmware source code for Orbi under GPL license or some custom very restricted license, community would fix these problems for them.
Glad i found these pages. Thought i was going nuts. Really wish i could return these units and get something stable as i'm running a business at my home and my router is in the basement. So everytime it fusses i have to go down 2 flights of stairs and restart the dang thing.
Have been using Netgear products for YEARS and never encountered a product of theirs so inept at it's core function.
Do the downgrade. It seems to be solid. We use the wifi not only for internet but also for our wireless Dish Joey's so no TV when it goes down too.
I am relying on ethernet backhaul. I'm assuming the downgrade doesnt support that? I have a 3 story house that i purchased as a new construction. I specifically ran wiring in the house for a mesh wifi system.
