NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AmitR
Mar 23, 2018NETGEAR Employee Retired
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 ...
Kyne
Mar 28, 2018Apprentice
Thanks, and awesome.
I am on 2.1.2.18 - will try the new beta this week as well and report back (also one of the few that has not had any issues with the current 2.1.2, and never went backwards)
Cheers
NickC4555
Mar 28, 2018Star
I'm still running beta V2.0.1.2. Noticeable differences between this and subsequent releases:
- 5Ghz band covers greater distance
- Faster WiFi speeds - Wi-Fi Sweetspots shows about 525Mbits/sec
- No disconnects
- Daisy chain works - later releases try to connect both sats to the router
I would urge the dev teams to go back to this as a stable release to build on and scrap other subsquent ones.
- timchMar 28, 2018LuminaryI for one see no need to scrap later releases. I have had excellent results from the 2.1 firmware. I am currently running an RBR 50 and RBS 50 on the 2.1.3 beta and an RBS40 on the 2.1.2.18. The RBS50 is connected by Wi-Fi backhaul and Ethernet for the 40. All is working fantastically with SweetSpots speeds above 800 throughout the house. I have all the options set apart from daisy chaining and I get great hand offs as I roam round the house. For the record I didn’t factory reset and the only snag I have had is my RBS50 connected to the RBS40 upon restarting after upgrade despite being closer to the router; hence I unselected daisy chaining.
- SharkSightMar 28, 2018Aspirant
I see no reason to scrap either. This beta and also the .18 builds ran fine for me and I have had no issues. So, scrapping a lot of work because of a pocket of user issues will just probably break things for those of us that are working. Not trying to down play the problems some users are having, but digging in and figuring out what makes the users who are having problems different is the way to solve this.
I would also be curious if electrical issues in a home can cause some of the user problems and reboots... inconsistent power can cause a lot of odd problems. Just a small power blip could be enough to cause a router to reboot or reset. I have all mine on small UPS boxes so if the power were to go out or flicker (which happens in CT from time to time in the winter or during heavy winds), that I don't have to worry about any of my network components going up or down or rebooting. Well... and if the power goes out for a few minutes and my whole house UPS isn't fired up yet... internet is still up and I don't have anyone complaining about no wifi. Heh.
- FURRYe38Mar 28, 2018Guru - Experienced User
Seems that v2.1.3.4 is the most stable out of anything so far. I presume once this has been tested fully, NG may push to this to auto FW updates depending if they need to make any other FW changes before then.
NickC4555wrote:I'm still running beta V2.0.1.2. Noticeable differences between this and subsequent releases:
- 5Ghz band covers greater distance
- Faster WiFi speeds - Wi-Fi Sweetspots shows about 525Mbits/sec
- No disconnects
- Daisy chain works - later releases try to connect both sats to the router
I would urge the dev teams to go back to this as a stable release to build on and scrap other subsquent ones.
- ckimmelshueMar 28, 2018Star
Fair point.
I'm all for ideas on how to resurrect my dead satellite. I have restarted it. I have hard reset it. I have tried another power supply. It just won't sync up. I am not paying Netgear $50 for the honors of helping me here when, in fact, their beta software broke it.
- wchpMar 28, 2018Luminary
ckimmelshuewrote:Fair point.
I'm all for ideas on how to resurrect my dead satellite. I have restarted it. I have hard reset it. I have tried another power supply. It just won't sync up. I am not paying Netgear $50 for the honors of helping me here when, in fact, their beta software broke it.
If you call support requesting an RMA warranty replacement they should not charge you. https://kb.netgear.com/1113/Warranty-Return-Policy
- Streak2Mar 28, 2018Master
ckimmelshue wrote:
Fair point.
I'm all for ideas on how to resurrect my dead satellite. I have restarted it. I have hard reset it. I have tried another power supply. It just won't sync up. I am not paying Netgear $50 for the honors of helping me here when, in fact, their beta software broke it.
You could try and connect to the satellite via ethernet cable and reflash the latest firmware for it.
- EpicBearMar 28, 2018Initiate
What device are you getting 800 mbps from WiFi on? My tests have only returned just above 500 at best!
- guzzijasonMar 29, 2018Apprentice
EpicBearwrote:What device are you getting 800 mbps from WiFi on? My tests have only returned just above 500 at best!
I think that "800" estimate was coming from the SweetSpots mobile app. I think that app does a good job of helping find strong/weak signal areas, but I don't know how accurate its WiFi speeds are, and they might not reflect "real world" speeds. Its entire test seems to consist of pumping UDP traffic at the router as fast as it can. It doesn't receive any data back via WiFi.
- steve8411Mar 29, 2018Apprentice
Oh well! So much for the static iP solution.
ipad lost connection.
IMO there is clearly a problem with DHCP vs mostly apple devices. Even with a static IP???
Rokus, no issue. IP cams, no issues. Wired devices, no issues.
- guzzijasonMar 29, 2018Apprentice
[deleted - wrong thread]
- FURRYe38Mar 29, 2018Guru - Experienced User
I use a reservation ON the router for my devices. my Iphone is working ok.
steve8411wrote:Oh well! So much for the static iP solution.
ipad lost connection.
IMO there is clearly a problem with DHCP vs mostly apple devices. Even with a static IP???
Rokus, no issue. IP cams, no issues. Wired devices, no issues.