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
NETGEAR SUCKS! ORBI SUCKS! LEARN TO CODE!
I am so sick of this piece of **bleep** called Orbi!!!Yes did it all 2.1.3.4 + countless factory resets etc.
Planetom wrote:NETGEAR SUCKS! ORBI SUCKS! LEARN TO CODE!
I am so sick of this piece of **bleep** called Orbi!!!Yes did it all 2.1.3.4 + countless factory resets etc.
return to sender
OK!!! I will say it again!!! What about the other models???? I mean it can't be that much different to mod the firmware for the other models. So 2.1.3.4 is working great for RBR50, Great!!!!!!! What about the other models???? It’s been two weeks since the beta was released?????? and it's being auto pushed to the 50 series. Getting tired of this if you can’t tell!
Chemo29 wrote:
OK!!! I will say it again!!! What about the other models???? I mean it can't be that much different to mod the firmware for the other models. So 2.1.3.4 is working great for RBR50, Great!!!!!!! What about the other models???? It’s been two weeks since the beta was released?????? and it's being auto pushed to the 50 series. Getting tired of this if you can’t tell!
Its not being auto pushed to anything anymore. Since it is a beta, I'm not sure why they were doing that in the first place. It is a bit of a muddle why it is taking so long, no visibility, so my shot in the dark is that they are going from most installed base items to least installed base items. The RBR50, RBS50 are by far the most installed, with the RBR40/RBS40 being second, and everything else a distant third.
The amount of time this is taking is really unacceptable, like many others I struggle with ongoing issues with this system and I can't install the beta as I have a different model.
I really want this to work as this system does have great potential,
Netgear if you can't fix these issues why not start offering those of us stuck an exchange program for a working system, it shouldn't take months to fix something unless it was truly flawed from the onset.
Best bet to keep an eye on this thread:
https://community.netgear.com/t5/Orbi/Orbi-MR-2-1-Update-3-23-18/m-p/1533584/highlight/true#M26234
and the official download web page.
May seen that is easy just changing some code. There a lot more that goes into FW development and testing.
Chemo29 wrote:
OK!!! I will say it again!!! What about the other models???? I mean it can't be that much different to mod the firmware for the other models. So 2.1.3.4 is working great for RBR50, Great!!!!!!! What about the other models???? It’s been two weeks since the beta was released?????? and it's being auto pushed to the 50 series. Getting tired of this if you can’t tell!
I work for Cisco enterprise routing and switching and it's not that hard to modify firmware for same platform systems. I bought Orbi for my home because it's a great idea to have the backplan across it's own dedicated backhaul. But this is just getting ridiculous!
Where is the new firmware for the RBR50Y (outdoor) satellite? I looked through the list, but that one doesn't seem to be covered.
splogue wrote:Where is the new firmware for the RBR50Y (outdoor) satellite? I looked through the list, but that one doesn't seem to be covered.
They haven't released it yet. I waited till 3 out of 4 of my components had the updated beta firmware and went ahead and upgraded. My system is working fine with the RBS50Y sitting at production firmware and the rest upgraded.
Gotcha - it appears to be an oversight. The RBS50-Y is internally the same as the RBS50. The firmware for it should be nearly identical, yet isn't on the released list.
Hi. Does anyone know if this update allows the character ‘ in the ssid name?
I did a factory reset after installing almost a week ago. Its been rock solid for me and no devices drop internet. Especially my iOS devices. I particularly had issues with them being connected but no internet.
My satellite did reboot once but I think that might have been power related. But other than that I haven't had any connection issues with any of my devices. Family has been quiet cuz before I used to hear why is this internet not working or its so slow(it really wasn't loading anything but wifi was connected).
So far I am pretty happy with this firmware.
Glad it's working well for you.Thanks for letting us know.
nkdwrote:I did a factory reset after installing almost a week ago. Its been rock solid for me and no devices drop internet. Especially my iOS devices. I particularly had issues with them being connected but no internet.
My satellite did reboot once but I think that might have been power related. But other than that I haven't had any connection issues with any of my devices. Family has been quiet cuz before I used to hear why is this internet not working or its so slow(it really wasn't loading anything but wifi was connected).
So far I am pretty happy with this firmware.
When are you guys finally going to support hard drive or flash drive support on the USB port? Would love to stream media off of it via ReadyShare
DezMwrote:When are you guys finally going to support hard drive or flash drive support on the USB port? Would love to stream media off of it via ReadyShare
This kind of thing tends to get lost in a thread like this. Start a new post and Title it FEATURE REQUEST and then others will give it a Thumbs Up to support the idea.
I just started a new one for a radio button to disable automatic firmware updates. See here: https://community.netgear.com/t5/Orbi/FEATURE-REQUEST-Ability-to-DISABLE-firmware-auto-update/m-p/1544862#M27364
"Provides protection for the MDNS packet flood issue"
Please check into this protection. Since installing this firmware I'm having nothing but problems with Apple Homekit devices that connect via Wifi/Ethernet (bluetooth devices that connect to my appletv homekit hub are OK). The devices flap between "No Response" and online in the Home app.
What FW version were you using before?
Has a factory reset been performed after you updated to this Beta? If not, please factory reset both router and Satellite(s) then setup from scratch.
eljarvisowrote:"Provides protection for the MDNS packet flood issue"
Please check into this protection. Since installing this firmware I'm having nothing but problems with Apple Homekit devices that connect via Wifi/Ethernet (bluetooth devices that connect to my appletv homekit hub are OK). The devices flap between "No Response" and online in the Home app.
Already did a factory reset. I was using whatever the last stable 2.0 firmware was. With all the **bleep**ing around i've had to do with this piece of **bleep** i'm thinking of grabbing an old Cisco ASA5505 from work and using the Orbis strictly in AP mode.
I asked about this and was told that while beta builds are made available, there are changes to FW and in between builds will and can effect how configurations are used on prior versions of FW. So for users installing any of the Beta builds, you need to perform a factory reset and set up both router and satellite(s) afterwards to ensure the new FW is seated well and no prior configurations will be in the mix. You need to set up from scratch, then save off a new configuration.
I was told that once the official FW is released and no longer Beta, then factory resets will not be needed after upgrading FW. The user configurations should persist and continue to work well after upgrading with official released FW.
Will Orbi systems be auto updated to beta builds? Because I have had my system auto updated to new firmwares in the past that has broken things and I had to roll back to older firmware and factory reset and manually install the new one in order for things to be stable. At this point I dont trust anything released by Netgear. Beta or official.
FURRYe38wrote:I asked about this and was told that while beta builds are made available, there are changes to FW and in between builds will and can effect how configurations are used on prior versions of FW. So for users installing any of the Beta builds, you need to perform a factory reset and set up both router and satellite(s) afterwards to ensure the new FW is seated well and no prior configurations will be in the mix. You need to set up from scratch, then save off a new configuration.
I was told that once the official FW is released and no longer Beta, then factory resets will not be needed after upgrading FW. The user configurations should persist and continue to work well after upgrading with official released FW.
Please review first post in this thread:
"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."
joelinhowrote:Will Orbi systems be auto updated to beta builds? Because I have had my system auto updated to new firmwares in the past that has broken things and I had to roll back to older firmware and factory reset and manually install the new one in order for things to be stable. At this point I dont trust anything released by Netgear. Beta or official.
FURRYe38wrote:I asked about this and was told that while beta builds are made available, there are changes to FW and in between builds will and can effect how configurations are used on prior versions of FW. So for users installing any of the Beta builds, you need to perform a factory reset and set up both router and satellite(s) afterwards to ensure the new FW is seated well and no prior configurations will be in the mix. You need to set up from scratch, then save off a new configuration.
I was told that once the official FW is released and no longer Beta, then factory resets will not be needed after upgrading FW. The user configurations should persist and continue to work well after upgrading with official released FW.
Just want to put it out there that I do use this sytem in Router mode, but I have it behind my ATT router (the ATT wireless is turned off and mine is hard wired to it and hands out wireless to the house on the 10.0.0.x network).
It's too bad this site doesn't have an option for user surveys. It'd be helpful if we knew problems were predominantly on systems in an early mfg run and/or how they were set up. Mine was purchased from Amazon at end of June 2017.
I recommend using the modems DMZ for your Orbi router while in router mode. This will help with any double NAT issues.
Yes, the reason your Orbi router sets up 10.x.x.x is that your ISP modems is using the same default 192.168.1.1 that most NG routers use. So during setup, the wizard will change the NG routers IP address pool to not conflict with the modesm IP address pool. You can change from 10.x.x.x to 192.168.0.1 if you like.
Havok_wrote:Just want to put it out there that I do use this sytem in Router mode, but I have it behind my ATT router (the ATT wireless is turned off and mine is hard wired to it and hands out wireless to the house on the 10.0.0.x network).
It's too bad this site doesn't have an option for user surveys. It'd be helpful if we knew problems were predominantly on systems in an early mfg run and/or how they were set up. Mine was purchased from Amazon at end of June 2017.
Hi FURRYe38, I want to put my Orbi in router mode (currently in AP mode) but I have a mandatory ISP-issued router, which I can't set in bridge mode. Does using the ISP router's DMZ for my Orbi while in router mode mean adding the 10.0.0.1 to the DMZ? Or do I assign/set a 192.168.1.x IP to the Orbi (from the ISP router?), then add this IP to the ISP router DMZ instead?
And are there any risks to using the Orbi in the ISP router's DMZ?
FURRYe38 wrote:I recommend using the modems DMZ for your Orbi router while in router mode. This will help with any double NAT issues.
Yes, the reason your Orbi router sets up 10.x.x.x is that your ISP modems is using the same default 192.168.1.1 that most NG routers use. So during setup, the wizard will change the NG routers IP address pool to not conflict with the modesm IP address pool. You can change from 10.x.x.x to 192.168.0.1 if you like.
- Our Orbi system worked perfectly on the last production firmware. On this latest firmware and a factory reset our HomeKit home automation setup has become unreliable. Inevitably the ecobee system, casetta, or hue will show offline / no response now.
Try disabling Beamforming, MIMO, Daisy Chain and or Fast Roaming?
bsholbrookwrote:
Our Orbi system worked perfectly on the last production firmware. On this latest firmware and a factory reset our HomeKit home automation setup has become unreliable. Inevitably the ecobee system, casetta, or hue will show offline / no response now.- All of these options are already turned off
