NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi MR 2.1 Update 3/23/18
Our teams are still working through the issues, but I wanted to provide a quick update on OrbiOS 2.1. We usually wait to release our software until it's available across all Orbi product lines, but in a departure from our normal processes, we’re going to the release BETA software for our products in a staggered manner. The first wave to be released are only for the RBR50 and RBS50, which is used in the RBK50 and RBK53 (Costco) kits. If you have a kit that includes a different hardware product (including RBK52W, RBK40 series or RBK30 series) or a RBK50 or RBK53 with an add-on satellite (RBS40, RBW30), please hang tight. We’re not quite done with it yet, but will update this thread when it’s ready.
Edit for clarity: This release supports both Circle & Ethernet backhaul
Edit2: Updated with the 2nd wave of firmware for RBR40, RBS40, RBR20 and RBS20. This supports the following SKUs: RBK40, RBK43, RBK44, RBK20, RBK22, RBK23.
Edit3: Updated for RBW30, to support RBK30, RBK33, RBK52W, and others
We’re not yet going to push this release this for auto-firmware upgrade, and will let you know before we do. If you have any questions, feel free to reach out to Support.
Rel Notes:
- Fixes issues where Internet access is not available on some devices, but available on others.
- Fixes an issue where Satellites get disconnected from Router
- Provides protection for the MDNS packet flood issue
- Addresses an issue where websites set to unmanaged are unreachable
- Multiple other connectivity & RF improvements
BETA MR 2.1.3 software can be found here:
RBR50: http://files.netgear-support.com/go/?a=d&i=rFfsb14M2q
RBS50: http://files.netgear-support.com/go/?a=d&i=0UBXh9aus6
RBR40: http://files.netgear-support.com/go/?a=d&i=dnNl6nqBSj
RBS40: http://files.netgear-support.com/go/?a=d&i=FEaFlGNCuW
RBW30: http://files.netgear-support.com/go/?a=d&i=x990UeDEdo
RBR20: http://files.netgear-support.com/go/?a=d&i=IOMUioMSLU
RBS20: http://files.netgear-support.com/go/?a=d&i=S5JDrBEG2f
How to do a manual firmware upgrade: https://kb.netgear.com/31573/How-do-I-manually-upgrade-firmware-on-my-Orbi-Satellite
Orbi Product Team
761 Replies
Starting today, was running 2.1.2.8 (the first one that could use circle parent controls) and had intermittent network issues. Also, was unable to do speedtest from the app or from the router web access. I haven't turned anything off or messed with anything, just looks like the satellites are dropping, or maybe the main router. Either way, i normally get a 250Mbps speed test, but it was down to less than 1Mbps and after updating to 2.1.3.4 I can get it up to 25Mbps... but still not 100%. Thoughts?
After updating FW, did you factory reset both router and satellite and set up from scratch? This is needed for this beta version of fw.
How far appart is the router from the satellites?
How big is your home? SQFt?
Try disabling MIMO, Daisy Chain, Fast roaming and IPv6.
What is the Mfr and model# of the ISP modem?
wegunterjr wrote:Starting today, was running 2.1.2.8 (the first one that could use circle parent controls) and had intermittent network issues. Also, was unable to do speedtest from the app or from the router web access. I haven't turned anything off or messed with anything, just looks like the satellites are dropping, or maybe the main router. Either way, i normally get a 250Mbps speed test, but it was down to less than 1Mbps and after updating to 2.1.3.4 I can get it up to 25Mbps... but still not 100%. Thoughts?
That was it! Thanks a ton. I didn't do a factory reset after updating. All good now!
so I have been following the hundreds of posts in this thread as well as those prior to this one and for me the only reliable fix has been to split the 2.4G and 5G SSID's using Telnet. No matter what has been tried (and before anyone says it, I have factory reset numberous times both via website and paperclip method as well as trying every possible combination of mu-mimo, fast roaming, beamforming and daisy chain) the only thing that works for me is splitting the SSID. With the SSID combined I get numerious drops or issues connecting to internet etc. The main thing with this firmware is that I haven't had to keep rebooting the satellite to get Internet back at times but all in all splitting the SSID (like we used to have th options back in v1.x of the firmware) is the most reliable but naturally that defeats some of the object of using a mesh type setup.
Pink doesn't mean the router is crashing necessarily. The poster hasn't proven weather or not if the ISP services and signal to his modem is working properly from the ISP. This needs to be checked first to ensure the signal from the ISP service thru the modem is to spec.
Page 18 LED Behavior:This device is junk. I'm tired of playing all the reset/update/reset games. I am currently on V2.1.3.4. After updating firmware on both devices, I reset both of them and its been up for just over 9 days (09:06:50). Running on 5G on the satellite, as I have no connection wired close by for wired backhaul.
And it locked up again. Wired works fine, devices attached to the router wireless work fine, devices attached to the satellite are connected (I can launch the orbi app from my phone and see status, everything appears to be fine. Wifi is connected on phones, laptops, etc, but not connecting to the internet. It seems like the satellite is the issue. There is no interference from 2.4g or 5g.
Do NOT ask me any questions about how far things are away from each other (it was up for 9 days), or ask me to reset the devices (this is not a tenable situation). I don't want to disconnect the satellite, either. If I wanted to do that I would have never bought this system.
There is something SERIOUSLY wrong with this Orbi system, and NETGEAR doesn't appear to be putting this on the front burner.
I work from home and have a lot of devices on wireless. I can't keep operating in this fashion. PLEASE, fix this system. I want to like it but NETGEAR is making it impossible.
https://community.netgear.com/t5/Orbi/Orbi-MR-2-1-Update-3-23-18/m-p/1549643/highlight/true#M28054
CyberExorcist wrote:This device is junk. I'm tired of playing all the reset/update/reset games. I am currently on V2.1.3.4. After updating firmware on both devices, I reset both of them and its been up for just over 9 days (09:06:50). Running on 5G on the satellite, as I have no connection wired close by for wired backhaul.
And it locked up again. Wired works fine, devices attached to the router wireless work fine, devices attached to the satellite are connected (I can launch the orbi app from my phone and see status, everything appears to be fine. Wifi is connected on phones, laptops, etc, but not connecting to the internet. It seems like the satellite is the issue. There is no interference from 2.4g or 5g.
Do NOT ask me any questions about how far things are away from each other (it was up for 9 days), or ask me to reset the devices (this is not a tenable situation). I don't want to disconnect the satellite, either. If I wanted to do that I would have never bought this system.
There is something SERIOUSLY wrong with this Orbi system, and NETGEAR doesn't appear to be putting this on the front burner.
I work from home and have a lot of devices on wireless. I can't keep operating in this fashion. PLEASE, fix this system. I want to like it but NETGEAR is making it impossible.
FURRYe38 wrote:Pink doesn't mean the router is crashing necessarily. The poster hasn't proven weather or not if the ISP services and signal to his modem is working properly from the ISP. This needs to be checked first to ensure the signal from the ISP service thru the modem is to spec.
Page 18 LED Behavior:most the time when the device crashes it goes pink - its pretty good at crashing every 14 hours on the dot now -- just check these forms once a day for a working firmware ..
How are you determining it's a crash?
Can you access the routers or satellies UI when this happens?
Ping 192.168.1.1 from a comrmand line?
You might enable some debug logging, someting to give to NG support...
If you feel this is a router or HW problem, I would recommend you contact NG support and talk to someone. This maybe beyond something that a FW update can fix.
Brain29 wrote:
FURRYe38 wrote:Pink doesn't mean the router is crashing necessarily. The poster hasn't proven weather or not if the ISP services and signal to his modem is working properly from the ISP. This needs to be checked first to ensure the signal from the ISP service thru the modem is to spec.
Page 18 LED Behavior:most the time when the device crashes it goes pink - its pretty good at crashing every 14 hours on the dot now -- just check these forms once a day for a working firmware ..
- Just installed the beta firmware v.2.1.3.6 for my RBW30 wallplug satellite. Previously did the Reset .... I can confirm that this round of firmware looks very good in terms of stability. Daisy chain, Ethernet backhaul, Beamforming & Fast Roaming are all enabled. Everything working fine now. Only minor issues observed like inability to do the Speed Test ... my guess is this will get re-enabled down the road.
Ok, questions on the 2.1.3.4 FW upgrade.
1. Since this is a beta, do I have to reinstall again once the final version is released? Is this imminent or will it take months to be released? My system is dropping wireless devices constantly so I have to do something.
2. I have 2 wired runs for the Ethernet backhaul for the 2 satellites with no switches in between those and the main router. I am on 2.0.1.4 currently so the ethernet lines are not connected yet. What are the step by step instructions to do this upgrade correctly given the way it is configured?
Let us know how it goes. Should work well for you.
Yes, Ng is aware of the speed test issues.
Chairman007 wrote:
Just installed the beta firmware v.2.1.3.6 for my RBW30 wallplug satellite. Previously did the Reset .... I can confirm that this round of firmware looks very good in terms of stability. Daisy chain, Ethernet backhaul, Beamforming & Fast Roaming are all enabled. Everything working fine now. Only minor issues observed like inability to do the Speed Test ... my guess is this will get re-enabled down the road.
I updated the router to 2.1.3.4 from 2.1.2.8 via remotely-VPNed to the router. I would strongly recommend against doing what i did. During the update process, i believe the firmware got corrupted so i could no longer VPN to it. Because i was thousands of miles away, there was no way for me to fix it remotely. When i got back home, i could see the SSID of the network but i could not connect to it. I had to factory reset the router and both satellites and configure them from scratch. Everything appears to be working OK now.
Ya, wireless or VPN would not be recommended for doing FW updates. Next time, you might have someone more locally help out on site if a FW is needed. Glad the reset got it working again. Enjoy.
ktula wrote:I updated the router to 2.1.3.4 from 2.1.2.8 via remotely-VPNed to the router. I would strongly recommend against doing what i did. During the update process, i believe the firmware got corrupted so i could no longer VPN to it. Because i was thousands of miles away, there was no way for me to fix it remotely. When i got back home, i could see the SSID of the network but i could not connect to it. I had to factory reset the router and both satellites and configure them from scratch. Everything appears to be working OK now.
I've upgraded my system (RBR50, RBS50, 2x RBS40, 1xRBW30) to the latest BETA. Only upgraded RBW30 just now, however for the other parts of my system (running the latest FW beta for slightly less than a week now) this has been the best and most stable release for me in a very long time!
I used to have intermittent issues with individual wifi clients losing connections (and sometimes refusing to reconnect properly without satellite/router reboot) while other clients also connected to the same router or satellite were continously working just fine. My wife's Macbook were one of the most heavily affected by this, and have been for a long time - and believe me that was not easily managed. :P
I'm very happy to say that this seems to be a thing of the past now.
With 2.1.3.4 update on the RBR50, RBS50 - seems to be working, but I am noticing an error in Parental Controls -> Disney Circle- it is now saying cannot connect to device. I updated a few days ago, and circle app on my phone connected again, but now it is not.
THoughts?
Have you factory reset both router and satellite and reset up the circle app again?
wegunterjr wrote:With 2.1.3.4 update on the RBR50, RBS50 - seems to be working, but I am noticing an error in Parental Controls -> Disney Circle- it is now saying cannot connect to device. I updated a few days ago, and circle app on my phone connected again, but now it is not.
THoughts?
I factory reset the router, but not the satellites. How do you reset those?
I did renable Disney Circle and then connected to it from the app..not sure if i did that right...
Just upgraded to 2.1.3.4 and did the paperclip reset. Reconfigured the network and all looks solid so far. Thanks for all the tips guys. Have not had any issues with Orbi yet and hope to continue the smooth sailing.
- Frequent internet connection loss over and over. Yes I followed all instructions including paper clip reset.
Why doesn't Netgear issue a test tool or is asking for log files?
This is what professional developers do.
PS
Did I mention I am in IT procurement at Deutsche Bahn, Germany's biggest employer?- I agree. We are testing a beta but lack a feedback mechanism to expedite fault investigation and fix.
I tried support but the response was 'where did you get the beta?' and a request to change WiFi channel.This thread is the feedback mechanism.
You can send messages to the form moderators as well if you like.
Bullyterrier wrote:
I agree. We are testing a beta but lack a feedback mechanism to expedite fault investigation and fix.
I tried support but the response was 'where did you get the beta?' and a request to change WiFi channel.
I'm having an issue with an older Lenovo Laptop with a Broadband N Wireless Adaptor that arbitrarily drops the Internet (still connected to the WiFi - but drops Internet) - it's an older 1x1 adaptor connected to 2.4GHZ.
Tried the usual - turn off BeamForming, MU-MIMO, Fast Roaming.... I also tried fixed 2.4 Channel and Static IP on Laptop....
I did hard paperclip reset and reconfigure 2x - just to be sure. Both Router & Sat running 2.1.3.4
There was a mention of turning of 40 Mhz Coexistence - so will try that - but any other ideas?
What is the model # of the laptop. I have an x61, dual band adapter. Windows 7 x32.
What channels are you using? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any other wireless neighbors near by? If so, how many?
I have beamforming enabled on mine only.
Let us know if disabling 20/40Mhz does anything.
EDR1 wrote:I'm having an issue with an older Lenovo Laptop with a Broadband N Wireless Adaptor that arbitrarily drops the Internet (still connected to the WiFi - but drops Internet) - it's an older 1x1 adaptor connected to 2.4GHZ.
Tried the usual - turn off BeamForming, MU-MIMO, Fast Roaming.... I also tried fixed 2.4 Channel and Static IP on Laptop....
I did hard paperclip reset and reconfigure 2x - just to be sure. Both Router & Sat running 2.1.3.4
There was a mention of turning of 40 Mhz Coexistence - so will try that - but any other ideas?
- As for the ethernet connection, signal hops over 2 switches. No problem so far, as for thr backhaul.
Drops / internet connection loss still on.
As I stated before, a tool analyzing the configuration - hence indicating misconfigurations - would stop the guessing.
Netgear isn't listening.What is the Mfr and model# of these two switches?
So is the system working now currently:?
"Drops / internet connection loss still on." This mean connection loss is still happening?
How do you know NG isn't listening?
Planetom wrote:
As for the ethernet connection, signal hops over 2 switches. No problem so far, as for thr backhaul.
Drops / internet connection loss still on.
As I stated before, a tool analyzing the configuration - hence indicating misconfigurations - would stop the guessing.
Netgear isn't listening.
