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
I have updated my two RBS50 satellites and the RBR50 router to 2.1.3.4. Now, one satellite won't sync, and the other shows a backhaul of "Poor". Before, I had "Good" for both satellites. I did have multiple dropouts, however. These units have been problematic for me since day one with multiple firmware updates and excuses from NetGear.
I factory reset the router and both satellites 3 times now with the same results. I'm dont wasting my time with these.
NetGear - get your **bleep** together. What a terrible product. I will donate these to Goodwill.
DO a FULL FACTORY RESET on the ROUTER and SATELLITE(S)!!!
ckimmelshuewrote:I have updated my two RBS50 satellites and the RBR50 router to 2.1.3.4. Now, one satellite won't sync, and the other shows a backhaul of "Poor". Before, I had "Good" for both satellites. I did have multiple dropouts, however. These units have been problematic for me since day one with multiple firmware updates and excuses from NetGear.
I factory reset the router and both satellites 3 times now with the same results. I'm dont wasting my time with these.
NetGear - get your **bleep** together. What a terrible product. I will donate these to Goodwill.
I did, and I'm done doing them now. Crap product with even crappier firm and software.
ckimmelshuewrote:I have updated my two RBS50 satellites and the RBR50 router to 2.1.3.4. Now, one satellite won't sync, and the other shows a backhaul of "Poor". Before, I had "Good" for both satellites. I did have multiple dropouts, however. These units have been problematic for me since day one with multiple firmware updates and excuses from NetGear.
I factory reset the router and both satellites 3 times now with the same results. I'm dont wasting my time with these.
NetGear - get your **bleep** together. What a terrible product. I will donate these to Goodwill.
Just reboot your sats.
I performed several hard and soft reboots/restarts, to no avail.
- If this system does not start working like it should then I'm going to return it tomorrow. I really want to like this system but I also need it to work.
Oh well, made it 24 hours and connections dropped for multiple devices.
send them back to the room....
2 iPads and an android phone..
Personally wondering if there’s an issue with the DHCP from the router when jumping from sat to router and vice versa
For the most part, my setup has been pretty stable on v2.1.2.18; however, lately I have occasionally noticed connectivity drops on mobile devices, usually manifesting itself as a failure to obtain a DHCP lease.
Today, I updated to the beta v2.1.3.4 (including factory reset of satellites *only*). Will see if this affects the DHCP problems I was seeing.The router needs to be factory reset as well and is encouraged to ensure a good set up of the new FW.
guzzijasonwrote:For the most part, my setup has been pretty stable on v2.1.2.18; however, lately I have occasionally noticed connectivity drops on mobile devices, usually manifesting itself as a failure to obtain a DHCP lease.
Today, I updated to the beta v2.1.3.4 (including factory reset of satellites *only*). Will see if this affects the DHCP problems I was seeing.
Upgraded to the Beta Firmware for both the router and satellite. The satellite is connected to router in 2.4 GHZ and the connection is poor. Any solution for this, other than moving the satellite closer to the router. Satellite is exactly in a floor below the router.
Besure that you preformed a factory reset after loading the beta FW on BOTH router and Satellite. Then set from scratch.
Placement is crucial as well. Mines about 40 feet disstance between the router and satellite.
srinivas29wrote:Upgraded to the Beta Firmware for both the router and satellite. The satellite is connected to router in 2.4 GHZ and the connection is poor. Any solution for this, other than moving the satellite closer to the router. Satellite is exactly in a floor below the router.
I did for the satellite, I will have to do for the router. By Factory reset i hope you are asking me to hold the reset button on back of the router for 5 secs?
srinivas29wrote:Upgraded to the Beta Firmware for both the router and satellite. The satellite is connected to router in 2.4 GHZ and the connection is poor. Any solution for this, other than moving the satellite closer to the router. Satellite is exactly in a floor below the router.
You should try moving the satellite, at least as a troubleshooting measure. 5 GHz is absolutely terrible at penetrating walls/floors, so it's not terribly surprising to me that 2.4 GHz might win in this situation.
Been running fine on the 2.1.2.18 firmware, upgraded this morning about 4am and no issues with the upgrade, router, sat or devices. Been running fine so far. Will continue to monitor
- I just bought this system a couple of days ago and getting ready to send back. It will keep disconnecting and the download speed is lower then what it should be. Any way to fix these issues before I send it back?
Thank you
Csanderson0628wrote:
I just bought this system a couple of days ago and getting ready to send back. It will keep disconnecting and the download speed is lower then what it should be. Any way to fix these issues before I send it back?
Thank youTry the new "beta" firmware. See the first post in this series...
- I did try that link to update it but it would not take that update.
Csanderson0628wrote:
I just bought this system a couple of days ago and getting ready to send back. It will keep disconnecting and the download speed is lower then what it should be. Any way to fix these issues before I send it back?
Thank youWell, give the beta firmware a try for sure. Only for the RBR50/RBS50 (RBK53 set) for now. I was stable with previous firmware but many others had issues.
I have a linear configuration: Router-Sat1–Sat2. I cannot get Sat2 to connect to Sat1 in daisy chain configuration. Any way to force this? Sat2 and Router are at opposite ends with Sat1 in the middle.
- Is there a newer version for the RBS50Y Outdoor Satellite also?
- I have the same question: Does the Orbi Outdoor satellite (RBS50Y) work with the 2.1.3.4 Beta firmware. The current firmware version of the RBS50Y I have is: v2.1.2.20
I believe AmitR mentioned that the firmware number for the router and each satellite should be the same to the 3rd digit. I’m wondering if that applies to the RBS50Y as well?
Is there a version for RBS40? Or is it the same?
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.
Ok, here is a rough 1st test. Not quite idea test configuration. Just a laptop connected wired thru two switches.
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.
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.
Firmware loaded up, all the fancy options turned back on. Here goes nothing!
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.
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.
- 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
b1ggjoewrote:
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?It is worrisome that the exported .CFG file is binary and not text. To me, that suggests that importing the .CFG will, as you say, eliminate the benefits of a factory reset because it's just reading old settings back into memory. If the .CFG file were text, at least we would know what was in there and understand that the firmware was interpreting the old settings from text back into binary.
