NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Your experience with Firmware 2.2.1.210 released as of 10/3/18
The other long thread on the new firmware is useless and has become a tech support thread. Please only post your experience after upgrading to the new firmware, good or bad. I'd like to see everyone's feedback only to judge if this release is worth upgrading to or not. If you are having issues please open a new thread for support.
250 Replies
Users should keep posting in this thread, regarless of good or bad experiences:
Helps to keep posts about this version of FW central and so users and NG support and see whats going on. Instead of having posts all over the the place.
This update was applied automatically and a taken my one satellite offline. It's in "config sync" mode. I definently did not choose to apply this update.
Even a hardware reset has not solved the issue. Tonight I will reinstall the older firmware.
- This latest firmware bricked my RBR50 router. After around 3 hours and 3 phone calls with NETGEAR yesterday, they are sending me a replacement router.
Symptoms after the firmware update (accomplished via iOS Orbi app)...below is a condensed listing of what happened.
— App said Update was complete, and was reconnecting to WiFi.
— Tried several times (tapping Retry) in the app, but still couldn’t connect to WiFi.
— Checked available WiFi networks, and mine wasn’t listed.
— While on phone with NETGEAR, tried both a 30 second and 60 second reset on the router...WiFi signal never appeared.
— While on phone with NETGEAR, I connected an Ethernet cable between a PC and the router. Wasn’t able to access orbilogin.com.
— At this point, support said they’d done all they could, and the router will have to be replaced.
So there’s nothing more I can do until the replacement router arrives. (Am also hoping the satellite wasn’t bricked as well....won’t know until I try setting up the router).
FURRYe38 wrote:
Users should keep posting in this thread, regarless of good or bad experiences:
I beleive the first thread you mention was more intended as an announcement. Whereas the one started here is actually looking for experiences.
Never ending saga. Now satellite backhaul connection at 2.4. Also, satellite drops internet connection frequently. Skipped 2.1..4.16 for same reason. 2.1.4.10 works fine. Please don't ask about how my system is connected. The mere fact that this firmware update and the previous one don't work is all you need to know. I've had the system for about 1.5 years. Until 2.1.4.16 it worked fine. What a POS.
Did you manually update FW or use the auto update process. Auto update seems to cause problems. It's been recommended to manually download the FW files then apply them with a wired PC. Update the satellites first then the router then factory reset and set up from scratch. https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-released-as-of-10-3-18/m-p/1647303/highlight/true#M42416
Also any wifi neighbors year by?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials.
Tbsteph wrote:
Never ending saga. Now satellite backhaul connection at 2.4. Also, satellite drops internet connection frequently. Skipped 2.1..4.16 for same reason. 2.1.4.10 works fine. Please don't ask about how my system is connected. The mere fact that this firmware update and the previous one don't work is all you need to know. I've had the system for about 1.5 years. Until 2.1.4.16 it worked fine. What a POS.
Working great for me.
I have a RBR50 and an RBS50 and both upgraded fine. Same throughput and everything so far!
Enjoy. :smileywink:
soundersfc wrote:
Working great for me.
I have a RBR50 and an RBS50 and both upgraded fine. Same throughput and everything so far!
Ditto!
esiebert7625 wrote:
Please only post your experience after upgrading to the new firmware, good or bad. I'd like to see everyone's feedback only to judge if this release is worth upgrading to or not.
2.2.1.210 is working perfectly for me. All 3 Orbis updated fine except 1 satellite needed to be restarted. No factory reset required and all is well.
RocketSquirrel wrote:
2.2.1.210 is working perfectly for me. All 3 Orbis updated fine except 1 satellite needed to be restarted. No factory reset required and all is well.
I find I need to amend my statement after living with .210 for a while.
My iPad Air 2 disconnects from WiFi about once a day, dropping the connection for up to 30 seconds before it reconnects. This is while the iPad is stationary in one place.
It's easy to see because I disable cellular data while at home (one less radio to use battery power), so the iPad complains of lost connection. Other than that, my setup is working well.
My Orbi router is in AP mode behind an Asus AC68U router, and my 2 satellites are connected via Cat5e cable.
Is Daisy Chain enabled or disabled? Should be enabled on this version of FW.
Try try this?
Advanced Wireless Settings both 2.4GHz and 5GHz changed CTS/RTS Threshold to 2307.
https://community.netgear.com/t5/Orbi/Orbi-RBR40-RBS40-V2-1-4-16-mesh-network-drops-connection-to/m-p/1601598/highlight/true#M35230
Change the CTR/RTS threshold values for both 2.4 GHz and 5 GHz (2341 and 2345 respectively), changed preamble modes to long preamble, and Set 20/40Mhz Coexistence to 40Mhz only.
RocketSquirrel wrote:
RocketSquirrel wrote:
2.2.1.210 is working perfectly for me. All 3 Orbis updated fine except 1 satellite needed to be restarted. No factory reset required and all is well.
I find I need to amend my statement after living with .210 for a while.
My iPad Air 2 disconnects from WiFi about once a day, dropping the connection for up to 30 seconds before it reconnects. This is while the iPad is stationary in one place.
It's easy to see because I disable cellular data while at home (one less radio to use battery power), so the iPad complains of lost connection. Other than that, my setup is working well.
My Orbi router is in AP mode behind an Asus AC68U router, and my 2 satellites are connected via Cat5e cable.
TLDR: Updated without issue. Devices showing slightly decreased signal strengh but the wireless network has been up/down so it'll probably sort itself out after roaming a bit.
I manually updated tonight to work out any issues before next week and risk any unplanned outage from Orbi updating itself. I've had that happen in the past and I'm still mad about it. I wasn't looking for any specific features or fixes from this firmware. It's hard to get excited about release notes that say esentially "fixed some stuff" without going into detail about what was fixed. I'm used to release notes being dozens of pages long that details specifics... Netgear has major updates with 4 line release notes. haha!
Disclaimer: I have a nonstandard deployment in AP mode doing all the things that gives FURRYe38 nightmares...
Setup: I have the RBK53 in AP mode connected through a managed switch (yes... with IGMP snooping enabled!). My gateway is a pfsense sg3100 with the RBR50 as the Orbi "router" and two sats RBS50. L3 services such as gateway/routing, DHCP, DNS, mDNS/IGMP, etc. are all handled by my sg3100 firewall. Orbi has BEAMFORMING, MU-MIMO, and Fast Roaming enabled. 2.4GHz and 5GHz SSIDs split with different names. Daisy Chain is disabled. I'm wireless backhaul with pretty close proximity (4000 sq ft 3 floor home) with maybe 40 feet betwen the sats and the router. I have the router and one sat on either end of the middle floor. I have another sat in the middle of the top floor.
Update Experience: I've read to update sats before the router so I started to do that. I updated one RBS50 and it rebooted twice. No issue. Uploaded firmware to the other RBS50 but it timed out before I could complete the firmware upload (so I thought). Turns out the RBR50 (which I didn't upload firmware to) had decided to update itself. When the 3 devices came back up, they all reported updated firmware. 5G backhaul to the BRK50 like before. I did NOT perform a factory reset and have not for the past several firmware updates.
Before/After Testing: I have a Verizon FIOS 150/150Mbps connection. Download speeds before and after remained mostly the same 151/149 has been the average from my Samsung S9 over the last hour and a "quiet network" (everyone else is in bed) and I'm just listening to music. I ran some tests on DSL Reports before and I was getting A+ or A ratings for Overall, Bufferbloat and Quality. (I'm using pfsense + CoDel to manage my up/down bandwidth.) Bufferbloat rating went down a bit but tweaking the queue has helped a little bit. mDNS browser shows all my Google Home/minis, chromecasts, echos, wemo plugs, etc. are all back up. At first glance the majority of our devices are online... I normally see 40+ active devices during the day and tonight I only see 30 which is about normal for night.
Conclusion: If this stays the same... that will be 2 firmware updates without issue. Time will tell as to the stablilty but initial impressions are looking good. Family will put stability/streaming to the test with their devices over the weekend.
I updated my RBR50 and RBS50 manually on 03 Oct. I had no issues with the previous firmware except that I used to see occasional momentary loss of WiFi on my iPad when it was conected to the satellite. So far I have not seen this with the updated firmware but I think it's too early to say that it has definitely been eradicated.
2.2.1.210 made my sat useless.
Beta 2.2.1.204 has been stable for a week, no drops in wifi from router of sat, wireless backhaul.
Autoupdated from beta 2.2.1.204 to 2.2.1.210 via web gui, sat would not connect again. HW reset sat and removed sat from router web gui. Added sat again. All looked fine, no packet loss and backhaus status "good"
Lost wifi on sat 3 to 4 times pr. hour, router is still fine. Backhaul status is "poor" all the time, moving sat closer to router made no difference, backhaul will not connect via 5 Ghz and status is "poor"
Manual updated fw to 2.2.1.210 first on sat and the router. Factory reset and started over, all worked for 2 hours, backhaul 5 Ghz "good"
now sat loses connection to router 3 to 4 times pr. hour again. Wired backhaul is not an option for me and 2.2.1.204 was fine (the best to date)
Wifi on router is fine and has no drops but 2.2.1.210 made my sat useless.
This is a dream, not a mightmare Sir. Glad all is working for you. Your one less user I don't have to dream about. :smileywink:
This is just proof that Orbi DOES WORK!!!!
Enjoy. :smileyvery-happy:
netadmn wrote:
TLDR: Updated without issue. Devices showing slightly decreased signal strengh but the wireless network has been up/down so it'll probably sort itself out after roaming a bit.
I manually updated tonight to work out any issues before next week and risk any unplanned outage from Orbi updating itself. I've had that happen in the past and I'm still mad about it. I wasn't looking for any specific features or fixes from this firmware. It's hard to get excited about release notes that say esentially "fixed some stuff" without going into detail about what was fixed. I'm used to release notes being dozens of pages long that details specifics... Netgear has major updates with 4 line release notes. haha!
Disclaimer: I have a nonstandard deployment in AP mode doing all the things that gives FURRYe38 nightmares...
Setup: I have the RBK53 in AP mode connected through a managed switch (yes... with IGMP snooping enabled!). My gateway is a pfsense sg3100 with the RBR50 as the Orbi "router" and two sats RBS50. L3 services such as gateway/routing, DHCP, DNS, mDNS/IGMP, etc. are all handled by my sg3100 firewall. Orbi has BEAMFORMING, MU-MIMO, and Fast Roaming enabled. 2.4GHz and 5GHz SSIDs split with different names. Daisy Chain is disabled. I'm wireless backhaul with pretty close proximity (4000 sq ft 3 floor home) with maybe 40 feet betwen the sats and the router. I have the router and one sat on either end of the middle floor. I have another sat in the middle of the top floor.
Update Experience: I've read to update sats before the router so I started to do that. I updated one RBS50 and it rebooted twice. No issue. Uploaded firmware to the other RBS50 but it timed out before I could complete the firmware upload (so I thought). Turns out the RBR50 (which I didn't upload firmware to) had decided to update itself. When the 3 devices came back up, they all reported updated firmware. 5G backhaul to the BRK50 like before. I did NOT perform a factory reset and have not for the past several firmware updates.
Before/After Testing: I have a Verizon FIOS 150/150Mbps connection. Download speeds before and after remained mostly the same 151/149 has been the average from my Samsung S9 over the last hour and a "quiet network" (everyone else is in bed) and I'm just listening to music. I ran some tests on DSL Reports before and I was getting A+ or A ratings for Overall, Bufferbloat and Quality. (I'm using pfsense + CoDel to manage my up/down bandwidth.) Bufferbloat rating went down a bit but tweaking the queue has helped a little bit. mDNS browser shows all my Google Home/minis, chromecasts, echos, wemo plugs, etc. are all back up. At first glance the majority of our devices are online... I normally see 40+ active devices during the day and tonight I only see 30 which is about normal for night.
Conclusion: If this stays the same... that will be 2 firmware updates without issue. Time will tell as to the stablilty but initial impressions are looking good. Family will put stability/streaming to the test with their devices over the weekend.
FURRYe38 wrote:
This is a dream, not a mightmare Sir. Glad all is working for you. Your one less user I don't have to dream about. :smileywink:
This is just proof that Orbi DOES WORK!!!!
Orbi works well ONLY in AP mode. I can't see anybody having a stable system in Router mode! DHCP simply does not work! I hope that NG can look at those nasty stability issues. The product is not usuable with those issues!
Update went smoothly. However my two Carrier Infinity Touch thermostats lost connection and I could not get them to connect manually no matter what I tried. Every other device had no problem. I rolled back to 2.1.4.16 firmware, and they connected within minutes. They identify themselves as "Microchip Technology Inc.". Please fix this incompatability. I have a router and two satellites. When I check for networks to connect to it shows all three devices as separate networks. Three networks with the same SSID. I don't see this on any other clients.
The roll back procedure needs some work. When trying it with the cable modem connected the firmware kept going back to the latest version even after manually updating to the old firmware. I don't know if it was really, but the router kept insisting that is was on the latest 2.2.1.210 firmware. Once I disconnected the cable modem I was able to update everything back to 2.1.4.16.
This is not specific to this latest update, but I've noticed a lingering problem with my Orbi RBK50 system still exists:
Often (at least once a day on at least one device) I'm not getting a response when I surf to a website or social media site. I've found that turning WiFi off/on on the device cures the problem.
As this happens on my Macbook Pro, iPhone, iPad, and a Windows Surface Book 2, it can't be operating system specific....and the only common link I can think of is the WiFi network.
This is the problem most of us have had ....
This build seems to fix it.
Just want to update my post from 10/6. I had rolled back the firmware so my two Carrier Infinty Touch thermostats would connect since they would not with the new firmware. Well on 10/14 I got an email from the Carrier Server that my thermostats had not reported in for a while. I checked the router and found it had autoupdated to the new firmware. I disconncected the cable modem and tried to roll back the firmware again, but as soon as I connected the modem the router autoupdated the firmware again. TELL IT TO STOP AUTO UPDATING! I would but there is no way to turn it off. Horrible way to configure it. You HAVE to be able to roll back firmware when it breaks your network! I tried a factory reset but that did not help. I tried changing channels on the 2.4G network. I tried changing CTS/RTS threshold, changing MTU size, turning off 20/40 MHz coexistence. I tried turning off Daisy Chaining. All that did was give me a poor connection on the satellite furthest away. I do not have beam forming, MU-MIMO, or fast roaming enabled. I can get the thermostats to connect to the wifi by using the guest with no security, but they cannot connect to the Carrier server because it is not a secure connection. I need them to connect to the server for remote access and weather information, etc. I have never had anything like this happen in all the years I have had wireless. I have a $300 network router and I will have to add an access point to get my two thermostats back. All because I cannot roll back the firmware. What a joke.
Yep, super annoying that they just decided on their own to upgrade our firmware without our knowledge. It's screwed my devices up...and you can't even contact them thru their site without paying for support..der. All you can do is leave them a tweet but of course they wont reply to that either since it would be a free reply.
I have a similar problem. Any solutions yet?
Try a factory reset on the system. if this fails,
Try a Manual FW load:
https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-released-as-of-10-3-18/m-p/1647303/highlight/true#M42416Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
What WPA security modes are you using? Try using WPA2 and AES only.What is the Mfr and model# of the ISP modem the NG router is connected too?
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials.Try disabling the following and see:
MIMO, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s).If you updated to recent FW v.210, try enabling Daisy Chain. Some have mentioned that this seems to be working in reverse order, enabling means disabled actually.
AustinNative wrote:
I have a similar problem. Any solutions yet?
I updated today - just routine checking into the app (I'd upgraded my mobile) and it said to update, so I did: I have 3 satellites. It keeps showing "Current Firmware 2.2.1.210" and then "New Version Available 2.1.4.16" [huh???] a couple times I actually paid no attention and just clicked "Update" -- later the same old routine. I am utterly confused that it seems to be in an endless loop of recommending an upgrade to an earlier version.
- Would love it if I could get wired backhaul to work. It doesn't seem like it should be that complicated really. If I connect the two devices via LAN cable they should easily see each other and switch to wired backhaul. Kinda like literally every other mesh setup out there.
How did you set up wired back haul? The satellites have to be connected wireless first, then connect 1 of the satelites to the back of the Orib router? Use good quality LAN cable. Cat 6 recommended. After connecting the two together, wait 5 minutes for the top led on the satllite to turn on BLUE. Do a IP address reservation for the satellite ON the router. Turn off this sallite and do same for the 2nd satellite if you have 2nd satellite. After you get them on as BLUE and IP address reservation, place them in there remote locations, connect the LAN cable there and turn the satellites on 1 at time till the top led turns on BLUE. Should work then.
Any network switches in the mix between the satellites and Orbi router? If so, Mfr and mode#?
cahiatt wrote:
Would love it if I could get wired backhaul to work. It doesn't seem like it should be that complicated really. If I connect the two devices via LAN cable they should easily see each other and switch to wired backhaul. Kinda like literally every other mesh setup out there.Since the upgrade I need to powercycle the orbi frequently as devices loose internet access. They connect, but cannot get to the internet.
What Mfr and model # modem are you using with the Orbi?
If you updated to recent FW v.210, try enabling Daisy Chain. Some have mentioned that this seems to be working in reverse order, enabling means disabled actually. Hoping NG support can have a look at this. So try this out as well.
https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-and-connection-problems-Skybell/m-p/1649275/highlight/true#M43001Try this:
a221 wrote:
Since the upgrade I need to powercycle the orbi frequently as devices loose internet access. They connect, but cannot get to the internet.
After updating automatically via the web interface, devices stopped switching from the main router to the satellite for the most part. Sometimes device would show as being connected to the satellite, but the connection typ was listed as unknow for anything showing there. A reset to factory contitions and setting up again from scratch resolved both of those issues.
I had visions of needing to revert to the previous firmware version and perhaps updating again manually, but that proved to be unnecessary.
