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 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?
- 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 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.
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...
Was rock solid on .18 firmware. Tried the beta and now the GUI isn't showing the satellites properly. Reset the satellite back to factory and gave it a couple of hours for it to "settle down". That didn't work. Going to reset router and satellite and see if the beta is at least as good as .18
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.
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
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?
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.
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
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.
- 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.
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.
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.
A day after updating, and so far no problems. The apparent issue I was having with iOS devices was very intermittent, though, so only time will tell. Will let it bake...
- The orbi mesh system has greatly improved our signal and speed in our 2,000 sq feet home, we have coverage in all rooms, however in the orbi app I do get satellites showing n/a or none, but the router shows them as being connected in the router Web page and all is good. We are on 2.0.0.56.
We hope the next beta available for your system will be even better.
markbaker007wrote:
The orbi mesh system has greatly improved our signal and speed in our 2,000 sq feet home, we have coverage in all rooms, however in the orbi app I do get satellites showing n/a or none, but the router shows them as being connected in the router Web page and all is good. We are on 2.0.0.56.Got this on Wednesday. Worked fine for almost 24 hours then dropped my internet connection. Switched back to my Velop and all was fine. They released this and I decidedx one more try. I reset the system reloaded the firmware and it seemed to be working pretty good. Then I started up on setting up my ring cameras and august locks. Both of therse reported a poor wifi strength. Which I thought was strange as I was within 20 feet of the satelite and it was on a wired backhaul. So I started looking into this some more and noticed standing within 8 feet of the Satelite both my ipad and iphone only got 2 bars on the signal strength.
I am pretty sure I am done with Netgear now. This is getting to be a pain each time they make a change to reset all this up just to find out they still did not get it done right. I have decided netgard products are not worth all this time. So its back in the box. I am not sured i even want to give this system to anyone i know. All it has been is trouble the last few months.
I installed this las night. So far its positive, but i can't comment further yet. I installed router and updated sattelites and did a factory reset on the router. Will have better idea in a week or so.
I am still going strong today sitting at about 48 hours total. All is goooooooooooooooooooood. Not sure why a few people are having such huge problems :-(. Just curious if the people having so much troubles have Apple products on the network? If so they are all probably smearing the network with there AppleTalk tryin to connect to AOL!!!!
- Positive feedback, the system works well for me, coverage is awesome, speed much better than I had with my existing BT HomeHub which claims to have the best WiFi coverage... Pah. I have no more buffering or jitter with steaming with my TV and stb box connected directly to the main orbi router, even our second stb in the bedroom connected to a satellite no longer buffers or jitters. All devices connected to the mesh report max speeds so I'm happy. Only issue is the orbi app still not seeing the satellites.. No mega deal but I would like to see them in the app. When it comes to updating I can do it via the router Web page until they fix the app unless its related to my environment but I doubt that.
- I have also noticed all of my smart home devices responding much quicker to commands than before, ok talking milliseconds but it makes a difference when using Alexa for example to issue voice commands which has also improved.
I did not have any problems with previous version, but I went ahead and updated to the beta.
Now on the satellite I am getting disconnects... but just one device. It's a La Crosse c84343 weather station. It constantly (like once a minute) disconnects and then comes back online and requests DHCP address. My log is now filled with DHCP messages from that device. If it helps, that device is quite close to the satellite.
I have not done a hard reset of the satellite - I will do that next.
So far, this seems to be my only issue with the beta (knock on wood) but like I say, this is a new issue.
Jeremyinsfwrote:Now on the satellite I am getting disconnects... but just one device. It's a La Crosse c84343 weather station. It constantly (like once a minute) disconnects and then comes back online and requests DHCP address. My log is now filled with DHCP messages from that device. If it helps, that device is quite close to the satellite.
This issue is particular to the La Crosse weather station. For whatever reason, it gets very confused when both a 2.4G and 5G share the same SSID.
If you call their support line and chat a bit you will hear this about other routers and brands that share a common SSID. The trick to get it working again is to turn off the SSID broadcast for 5G (under Advanced wireless setup), then factory reset the La Crosse, link it up to the 2.4G SSID (which is the only one now being broadcast), power cycle the LaCrosse once the setup is complete and then re-enable SSID broadcast on 5G.
Make sure you are running the latest firmware on the LaCrosse as well.
This is not an Orbi issue but rather a LaCrosse issue that they are aware of.
Thanks for the info. Will definitely do what you suggest. However - why is this now a problem with the Orbi firmware update, when I had no problems before?
My guess is there is something wrong with DHCP ....
You cannot set lease times ... which, at my office, days after people are gone, their device still shows up as "connected"
So far, my Ipad has not had a problem after giving it a static IP.
steve8411wrote:My guess is there is something wrong with DHCP ....
You cannot set lease times ... which, at my office, days after people are gone, their device still shows up as "connected"
So far, my Ipad has not had a problem after giving it a static IP.
The default DHCP lease time on the Orbi is 1 day (86400 seconds). It can be changed, but you need to be on the command line to do it:
# config set lan_lease=86400 # config commit [ now reboot the router to apply]
Just change the default value to whatever you want... with the usual caveat that if you are poking around on the command line and not sure what you are doing, you may just make things worse for yourself; but nonetheless, the option is there for those intrepid types.
EDIT TO ADD: I'm not sure that extending the DHCP lease time will actually fix anything in regards to the intermittent connectity drops that some clients seem to have. Personally, I prefer a longer lease time, but I've seen clients drop their connetion well before the current lease expires.
Do a reset on both Satellite and router.
Also can try disabling MIMO, Daisy Chain and Fast Roaming to see if this helps any.
Jeremyinsfwrote:I did not have any problems with previous version, but I went ahead and updated to the beta.
Now on the satellite I am getting disconnects... but just one device. It's a La Crosse c84343 weather station. It constantly (like once a minute) disconnects and then comes back online and requests DHCP address. My log is now filled with DHCP messages from that device. If it helps, that device is quite close to the satellite.
I have not done a hard reset of the satellite - I will do that next.
So far, this seems to be my only issue with the beta (knock on wood) but like I say, this is a new issue.
