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
Thanks, Netgear team. I'm on 2.0.1.4 currently and having disconnect issues. Will download betas now and report back after some time testing it.
Downgraded from the 2.2 Beta successfully. Was a bit disappointed to see a release in the 2.1 series which means that wired backhaul is still not supported. Was also wishing for new fearures, like sharing USB drive and QOS control. Guess it was too much to wish for.
On another note I was shopping at a Target today and noticed the RBK30 for $199.00. That is a $50 markdown...
I think it's good that they limit scope to fixes and stabilization, rather than new features for now.
doccelo wrote:
Thanks, Netgear team. I'm on 2.0.1.4 currently and having disconnect issues. Will download betas now and report back after some time testing it.
I am still having issues with the router losing internet connectivity and in order to restore functionality I have to reboot the system manually. I've tried every suggestion I could find on these forums to no avail. It seemed stable for a while, but the issue of losing internet connectivity has returned and actually seems to be happening more frequently. Not sure where to go from here... (Yes, I did factory reset and set up from scratch for those wondering).
What model Orbi system do you have?
What is the mfr and model# of the ISP modem the Orbi is connected too?
When you say disconnects from the internet, do you mean you loose wifi connections or do you loose both wired and wireless?
There any indication on the routers web page of the internet status when this happens?
Do you still have access to the routers web page when this happens?
What channels are you using on the router for wireless?
Do you have the satellite connected? if so, what distance is the satellite away from the router?
doccelo wrote:doccelo wrote:
Thanks, Netgear team. I'm on 2.0.1.4 currently and having disconnect issues. Will download betas now and report back after some time testing it.
I am still having issues with the router losing internet connectivity and in order to restore functionality I have to reboot the system manually. I've tried every suggestion I could find on these forums to no avail. It seemed stable for a while, but the issue of losing internet connectivity has returned and actually seems to be happening more frequently. Not sure where to go from here... (Yes, I did factory reset and set up from scratch for those wondering).
Same problem here. Several of my home automation products stopped connecting after this update. Need fix ASAP!!! How can I reverse this upgrade to previous version?
QUESTION FOR NETGEAR - ATTN AmitR
Is the recommended procedure to update the satellites, then the router to V2.1.3.4...
and then hard reset (paperclip) the satellites and router after they come back up after the update...
and manually configure them from scratch to eliminate any old settings (that may carry forward) that are not applicable to this version of firmware?
I don;t think you have to hard reset the satellites. I have had it done for about 12 hours now and only thing I did was factory reset the router adn updated the satellites.
- I did hard reset them at first because I thought they had lost their association with the router, but it seemed that they did actually connect to the router but I couldn't see it in the orbi app. Logging into the Web page of the router shown that they were in fact connect perfectly fine. I think the orbi app needs some tweaking because it says satellites n/a when they are connected fine.
Hello Netgear,
Just so that I understand, for the RBK50 firmware;
Does the RBK50 (Orbi Router) Firmware Version 2.1.2.18 support Ethernet Backhaul still?
Does the RBK50 BETA MR 2.1.3 Firmware, support Ethernet Backhaul?
Thanks!
BJ
- Yes it does support Ethernet backhaul.
here goes nothing...
- I just updated my RBR50 and RBS50 to this beta firmware. My iProducts drop all the time. Hoping this fixes the issue!!! Very hopeful.
Updated from the 2.1.2.18 beta easily enough, no issues there. However, ethernet backhaul doesn't work. First attempt took the system down initially when I plugged in the cable. Eventually it recovered, but device list was showing satellite connected via 2.4g. Rebooted everything, disconnected satellite ethernet, everything came back ok. Reconnected ethernet to satellite, and took system down again. This time, it didn't recover on it's own and I had to disconnect satellite ethernet. Once disconnected, system immediately came back up.
I've noticed that when you plug in the ethernet cable, it takes about a minute or two to get going again. You might give it more time.
Is there any network Gb switches in between the Satellite and router? If so, what is the Mfr and model# and is it a managed or non managed switch. I have two in between my Satellite and it took a good minute or two to get going. Been up and running. My switches are not managed however.
Prelectorwrote:Updated from the 2.1.2.18 beta easily enough, no issues there. However, ethernet backhaul doesn't work. First attempt took the system down initially when I plugged in the cable. Eventually it recovered, but device list was showing satellite connected via 2.4g. Rebooted everything, disconnected satellite ethernet, everything came back ok. Reconnected ethernet to satellite, and took system down again. This time, it didn't recover on it's own and I had to disconnect satellite ethernet. Once disconnected, system immediately came back up.
I gave it a good 10 minutes each try to stabilize, but no joy. I didn't do a hard reset, because of the time to readdress things. I'll likely sit at this point with wireless backhaul until I see some empirical evidence it's working in this version.
Came from stable 2.1.2.18 with one sat using ethernet backhaul, the second sat using wifi backhaul. After upgrading to latest beta I had to unplug ethernet backhaul for the system to stabalize. Not sure if the new FW is an improvement over 2.1.2.18 for me. Time will show.
I've noticed that when you plug in the ethernet cable, it takes about a minute or two to get going again. You might give it more time.
Is there any network Gb switches in between the Satellite and router? If so, what is the Mfr and model# and is it a managed or non managed switch.
Did you also factory reset the router and satellite after applying the new Beta FW and set up from scratch?
joknutsenwrote:Came from stable 2.1.2.18 with one sat using ethernet backhaul, the second sat using wifi backhaul. After upgrading to latest beta I had to unplug ethernet backhaul for the system to stabalize. Not sure if the new FW is an improvement over 2.1.2.18 for me. Time will show.
I’m surprised this beta release is a 2.1 and not a 2.2. Is 2.2 now a dead end? It’s working fine for me in terms of network stability. The only bugs I see are in the GUI, not the network.
I’d love to know whether this 2.1.3.4 improves upon my 2.2.0.30-20180221, and if so, how?
I highly recommend doing a Factory reset after installing the beta FW. This probably has major changes and updates to the code. To ensure the beta FW is installed and seated well and to give it a solid chance, a factory reset should be performed and set up from scratch. I can attest to ethernet back haul IS working on my Orbi system. Factory reset performed and then set up from scratch. Two non managed Gb network switches between my 1 Satellite and the Orbi router.
Give the new FW a chance. Take the time and do the reset and set up from scratch.
- I’m curious:
Doesn’t Orbi have a way to Export a config file of all of our settings, that we can simply reimport after a Factory reset?
Even if it does, I wonder then, if by doing so would just eliminate any of the benefits of doing a Factory Reset to begin with?
Also, is it just me or is it that we can only disable SSID Broadcasting from the Guest Network, but not from the main WiFi Network?
They also need to add a way to force WiFi devices to only connect to either 2.4GHz or 5GHz.
BJYes under Advanced/Backup settings. Under normal circumstances and with in the same version of FW, this back up file is valid. However after updating FW from one version to the next major version, there maybe some items with in the new FW that could have adverse operations if a older config file is applied from a prior version of FW. So, with this, I recommend after upgrading to the next major version of FW or Beta or from Beta to official releaed FW. Do a factory reset, set up from scratch and then save off a new back up config file for this next version thats loaded. Then you have a good back up for the current version of FW that your working with. Seen odd issues over the years in working with routers and configurations and many different FW versions. All this lead me to just take the plunge and do a resets then set up from scratch and make a new backup config file at each upgrade stage in the FW cycle. I presume when the FW become more stable and all non beta official FW, you mgiht be able to just upgrade the FW and any current configurations should remain and persist which is NG normal idea of upgrading FW.
You should be able to disable the main wifi radios under Advanced/Advanced/Wireless settings. Is this what your looking for?
The Orbi system is designed Smart Connect. It's supposed to handle which devices get connected to which freqency based on device support and operation automatically. So this feature isn't supposed to rely on any user intervention.
b1ggjoewrote:
I’m curious:
Doesn’t Orbi have a way to Export a config file of all of our settings, that we can simply reimport after a Factory reset?
Even if it does, I wonder then, if by doing so would just eliminate any of the benefits of doing a Factory Reset to begin with?
Also, is it just me or is it that we can only disable SSID Broadcasting from the Guest Network, but not from the main WiFi Network?
They also need to add a way to force WiFi devices to only connect to either 2.4GHz or 5GHz.
BJ
Well, 16 hours up time on the new firmware with..
Daisy-Chain Topology enabledImplicit BEAMFORMING enabled
MU-MIMO enabled
Fast Roaming enabled.
I have the RBR50 and two RBS50s. So far everything is working flawless! *knocks on wood*. I didn't go as far as factory resetting everything, just updated that sats, then the routers. Figured I'd try that before resetting everything. So far so good, no errors in the logs, no issues on any devices. Best stability I've had in months.
YAY!!! :smileyvery-happy:
TrickyTwrote:Well, 16 hours up time on the new firmware with..
Daisy-Chain Topology enabledImplicit BEAMFORMING enabled
MU-MIMO enabled
Fast Roaming enabled.
I have the RBR50 and two RBS50s. So far everything is working flawless! *knocks on wood*. I didn't go as far as factory resetting everything, just updated that sats, then the routers. Figured I'd try that before resetting everything. So far so good, no errors in the logs, no issues on any devices. Best stability I've had in months.
Firmware loaded up, all the fancy options turned back on. Here goes nothing!
So I gave this beta a test run and disappointingly the packet loss issues are still there. As you can see from the graph, the communication hangs at regular intervals. This is a 10 minute graph with a massive 16.8% PL. For this test I tried several configuration combinations, factory reset and disconecting all devices from the network in order to isolate the issue to the Orbi devices. I have been doing this for each firmware version since 2.0.0.74
This issue began wirh firmware V2.0.1.4 with only a mild PL issue. Newer firmwares have been just as bad as the current beta. Fortunately I don't need Circle or ethernet backhaul so I'm goinga back to V2.0.0.74 for the time being.
I loaded this up about 3 hours ago. At first I had the same problem as some people with the satelites bringing down the whole network until I did this, hope it helps someone.
1. Held down the factory reset button on each satelite till the power led started blinking amber (I did NOT factory reset the router, but will if I have any troubles).
2. Once I saw that it was in process of rebooting, I plugged in my ethernet cable for ethernet backhaul
3. Once each satelite booted back up I could see in the "Attached Devices" page the satelites had a status of "sync config" (or somethng close to that). Obviously it was getting its setting back from the RBR.
4. Everything has been perfect after that so far.
Here is my setup:
1 - RBR50
2 - RBS50's (both of them are hooked up to a Netgear GS108 switch along with a few PC's and DirecTV boxes, then a single cable going from switch to the RBR50.
Also something worth noting, I reserved permanent IP's for my 2 satellites.
- Thank you for the suggestion. I did paperclip factory reset of the sat's but not the router, and it did settle down the system. I am now able to run one sat with Ethernet backhaul, and one over WiFi (and they daisy chain). I am no longer experiencing drops and cycling of backhaul connection between router and sat
What version of test software are you using?
What PC HW are you using?
What version of Mac or Windows are you using?
Any security software enabled on this PC?
PyroDog wrote:So I gave this beta a test run and disappointingly the packet loss issues are still there. As you can see from the graph, the communication hangs at regular intervals. This is a 10 minute graph with a massive 16.8% PL. For this test I tried several configuration combinations, factory reset and disconecting all devices from the network in order to isolate the issue to the Orbi devices. I have been doing this for each firmware version since 2.0.0.74
This issue began wirh firmware V2.0.1.4 with only a mild PL issue. Newer firmwares have been just as bad as the current beta. Fortunately I don't need Circle or ethernet backhaul so I'm goinga back to V2.0.0.74 for the time being.
And what is the Mfr and model # of the ISP modem your using with the orbi system?
PyroDog wrote:So I gave this beta a test run and disappointingly the packet loss issues are still there. As you can see from the graph, the communication hangs at regular intervals. This is a 10 minute graph with a massive 16.8% PL. For this test I tried several configuration combinations, factory reset and disconecting all devices from the network in order to isolate the issue to the Orbi devices. I have been doing this for each firmware version since 2.0.0.74
This issue began wirh firmware V2.0.1.4 with only a mild PL issue. Newer firmwares have been just as bad as the current beta. Fortunately I don't need Circle or ethernet backhaul so I'm goinga back to V2.0.0.74 for the time being.
Is there a version for RBS40? Or is it the same?
