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
I had big hopes that the 2.2.1.210 software would solve the wifi dosconnections. I was told by Netgear support that the issue is solved in latest beta 2 weeks ago, but it seems that it's not, now that I have 2.2.1.210!
Once or twice a day, all my devices will drop wifi connection and will show 169. address.
The only thing that solves this issue is to switch off the Satellite, wait until all devices get wifi connection to the router and then switch on the Satellite.
Changing to wired backhaul improved the situation but did not solve it, so I'm getting this issue 1-2 times a day instead of 5-6 times a day with the wireless backhaul.
This is really very disappointing!
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. This is for wireless connected satellites only and problems seen with them.
- Daisy Chain is enabled in my case, and I can see this by seeing that there are 2 hidden 5 GHz backhaul networks (one from each node, in my case one from the router and one from the satellite). I tried disabling Daisy Chain (in this case you will only see one hidden 5 GHz backhaul network from the router) but that did not help. Anyway, I have wired backhaul and only one Satellite so Daisy Chain should not have any role here :)
FURRYe38 wrote: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.
Regarding the daisy chain issue after the inital download: I downloaded the update again from the Netgear site and reinstalled manually due to poor backhaul when daisy chain is off. This changed nothing. However with daisy chain on, the system is selecting star connection (hub and spokes). For my set up, the daisy chain on puts the system into a "select best" mode. With daisy chain off the system seems not to really know which way to go. Before the update, daisy chain on gave poor backhaul. Now it seems to only work well when on, and then the system selects a star pattern as the best connection.
It's a feature.
RBR50 and RBS50. Router mode. Wireless backhaul. No problems whatsoever. I've been very lucky, I guess. I've never encountered any of the problems discussed in this forum. My Orbi system just works great. Always has. Also, I've never done a factory reset after any firmware update.
Thanks for letting us know.
Enjoy. :smileywink:
snellc001 wrote:
RBR50 and RBS50. Router mode. Wireless backhaul. No problems whatsoever. I've been very lucky, I guess. I've never encountered any of the problems discussed in this forum. My Orbi system just works great. Always has. Also, I've never done a factory reset after any firmware update.
snellc001 wrote:
RBR50 and RBS50. Router mode. Wireless backhaul. No problems whatsoever. I've been very lucky, I guess. I've never encountered any of the problems discussed in this forum. My Orbi system just works great. Always has. Also, I've never done a factory reset after any firmware update.
snellc001 Can you please let us know more about your configuration, devices, modem, distances,... etc so as to compare and see if we can find where our issues are?
Thank you,
I have an RBR50 and a single RBS50. 2 story 2300 square foot house with the router in the master bedroom(second floor) and the satellite in the kitchen (first floor) about 50 feet away. I've been using router mode and wireless backhaul ever since I bought my Orbi. Devices typically connected are: 3 LG smart TV's, Sony and LG Bluray players, Amazon Fire TV, Amazon Kindle Oasis, an original Google Pixel phone running Android 9, and several iPhones (7 and 8), an Asus Windows laptop, an iPad, a MacBook Pro, and a 2018 Ford Escape (connects and updates when when in the driveway).
I have not had any issues in fact I did not know that my system was updated to this release until I checked after browsing the community site. The update was seamless as no one complained about noticing an outage (there are 4 of us plus friends and other family).
In terms of the environment, I live in a 2.5 story townhouse with a lot of neighbors also broadcasting wifi signals (I see over a dozen networks on my phones wifi signal strenght app). The Orbi runs in router mode attached to my Arris Surfboard SB6183 cable modem. IP service is from Spectrum. I have about 8 devices on all of the time not including phones, laptops and TVs. I don't know if it makes a difference, but I assigned specific IP addresses to the devices that were on most or all of the time. I use the range 148.192.168.0x for the Orbis, 148.192.168.1x for wired connections and start the DHCP range at 148.192.168.2x. I do not use remote management.
The only issue I am currently having has to do with the list of devices that are not currently connected. It reports almost every connection as having been wired when in fact they were wireless though one of the Orbi satellites.
Glad it's working for you.
Thats an odd IP address pool, however if it works for you. :smileywink:
Is Daisy Chaing Disabled or Enabled on your router? 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. May effect how devices are being reported. I believe that this may fix your one issue...
73Bruin wrote:
I have not had any issues in fact I did not know that my system was updated to this release until I checked after browsing the community site. The update was seamless as no one complained about noticing an outage (there are 4 of us plus friends and other family).
In terms of the environment, I live in a 2.5 story townhouse with a lot of neighbors also broadcasting wifi signals (I see over a dozen networks on my phones wifi signal strenght app). The Orbi runs in router mode attached to my Arris Surfboard SB6183 cable modem. IP service is from Spectrum. I have about 8 devices on all of the time not including phones, laptops and TVs. I don't know if it makes a difference, but I assigned specific IP addresses to the devices that were on most or all of the time. I use the range 148.192.168.0x for the Orbis, 148.192.168.1x for wired connections and start the DHCP range at 148.192.168.2x. I do not use remote management.
The only issue I am currently having has to do with the list of devices that are not currently connected. It reports almost every connection as having been wired when in fact they were wireless though one of the Orbi satellites.
I use specific IP asssignments because I wanted to avoid potential conflicts. The wired devices in my configuration are either always on (e.g. Ooma, Roku) or where I want to set a specific IP for administration (my laptop in wired mode).
My system has Daisy Chaining enabled (and always has since that functionality was enabled) but the devices are separated far enough so that they don't chain. I am looking at getting an additional RBS50 or 40 to speed up connectivity in our large kitchen), it would probably chain if I don't wired the boxes.
My Orbi has been a solid performer until this weekend. The main router seems to shut down every 6 hours without any guidance from me. I went to trouble shoot it tonight and realized it had auto installed the latest firmware on the router and satellite.
It looks like the back haul has been compromised by the firmware. Up till now my satellite noted the back haul was good, but tonight it notes poor.
I can't stay up and deal with this tonight, so I'll call for support tomorrow when I return from work.
Factory reset the base and satellite and set up from scratch...
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.What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?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.
StevenYago wrote:
My Orbi has been a solid performer until this weekend. The main router seems to shut down every 6 hours without any guidance from me. I went to trouble shoot it tonight and realized it had auto installed the latest firmware on the router and satellite.
It looks like the back haul has been compromised by the firmware. Up till now my satellite noted the back haul was good, but tonight it notes poor.
I can't stay up and deal with this tonight, so I'll call for support tomorrow when I return from work.
The Orbi is connected to an Arris TM822 Cable modem (Service is 200mb down/ 35 mb up)
I have a two-story 2,300 sg ft house. Router is on 1st floor and satellite is 2nd floor other side of house. The backhaul was good when it was first installed.
2.4 is auto (channel 4), 5 is on 48
Daisy chain & MIMO is active
Fast Roaming and IP6 is disabled
12 devices usually on network
My router is on router mode. Should that be changed to AP?
The system has been up for almost 13 days. No noticible performance issues but the router gui shows one of the satellites in perpetual config sync and one of the devices on an unknown satellite (happens to be actually connected to the other satellite) and unknown connection type. Checking on both satellite gui's shows connections all ok and all connected devices properly identified with known connection types.
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#M43001
caremd99 wrote:
The system has been up for almost 13 days. No noticible performance issues but the router gui shows one of the satellites in perpetual config sync and one of the devices on an unknown satellite (happens to be actually connected to the other satellite) and unknown connection type. Checking on both satellite gui's shows connections all ok and all connected devices properly identified with known connection types.
I feel like a dummy now. Netgear tweeted me back with a link to download old firmware. I download 1.10 firmware that I last used that I know had no issues. I also uninstalled the Orbi app from my phone.
Downgraded and like magic all my Lifx bulbs are connected again. Installed the app and noticed an "upgrade" button next to the satellite that I don't remember noticing before and maybe...just maybe I clicked on it and actually set off the update to the latest my firmware myself lol. This time I made sure not to touch it. So after all that auto-update conspiracy talk, i probably did it myself by accident.
I will wait and see. I just downgraded 20 mins ago so we'll see if I stay at the 1.10 FW i'm at now without issues.
I bought this thing when it first came out, preordered through crutchfield. I believe the model was called RBK50 that came with both satellite and router. Until this firmware, I've never had an issue and have always just let the thing auto update. This time, it caused a few hiccups, a bunch of my random devices all of a sudden got blocked by access control even though they were allowed before. Also why does the RBW30 not get the latest firmware?
Over the life of my ownership, the RBW30s usually had different firmware versions (until the last update before this one). When I updated my system all my devices updated, with the 40s going to 2.2.1.210 and the 30s going to 2.2.1.204 from both at 2.1.4.16. This is perhaps because of the stripped down features on the RBW30s, like no ethernet ports (and so also wifif backhaul only) and perhaps indicating that some of the changes in the new 210 firmware had to do with wired system functions..
What is the Mfr and model# of the ISP modem the NG router is connected too?
.
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#M43001
milk242 wrote:
I bought this thing when it first came out, preordered through crutchfield. I believe the model was called RBK50 that came with both satellite and router. Until this firmware, I've never had an issue and have always just let the thing auto update. This time, it caused a few hiccups, a bunch of my random devices all of a sudden got blocked by access control even though they were allowed before. Also why does the RBW30 not get the latest firmware?
Do not upgrade to this version if possible! Router WiFi still works but neither of the two satellites can stay connected for long. Netgear support responded recently that this firmware IS having connectivity issues and they are working on a fix. Pretty poor for flagship product.
chappietx wrote:
Do not upgrade to this version if possible! Router WiFi still works but neither of the two satellites can stay connected for long. Netgear support responded recently that this firmware IS having connectivity issues and they are working on a fix. Pretty poor for flagship product.
This is an example of why you should try NOT to get too excited when your network crashes or disconnects. Short of a complete dead in the water system, your best bet is to leave it alone (re-boot as necessary) until the next FW update. We've been through auto-updates turned off and that didn't work. We receive wonderful suggestions about numerous rabbitt chasing ideas, i.e. what modem are you running, model #, FW version, etc, etc, etc. At the end of the day it all comes back to there is NO perfect soultion. There is NO one size fits all. With the number of ways I've seen/heard of people running a network and the number/types of devices connected, I'm not sure NG will ever get it figured out. Don't look for salvation else where for most of the other router makers operate the same way. Stay tuned and relax.
What is the Mfr and model# of the ISP modem the NG router is connected too?
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.
https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-and-connection-problems-Skybell/m-p/1649275/highlight/true#M43001Try a Manual FW load and try again:
https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-released-as-of-10-3-18/m-p/1647303/highlight/true#M42416
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.What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
chappietx wrote:
Do not upgrade to this version if possible! Router WiFi still works but neither of the two satellites can stay connected for long. Netgear support responded recently that this firmware IS having connectivity issues and they are working on a fix. Pretty poor for flagship product.
i bought the system and had to upgrade the firmware. Now i cant connect the satellite there is no responce at all. I had contact with support by phone and they said there was something wrong whit the new firmware. The backhaull is not functioning, the advice was to wait for the new firmware. There is still no new firmware. Is there another sollution to solf the problem?
Abke wrote:
i bought the system and had to upgrade the firmware. Now i cant connect the satellite there is no responce at all. I had contact with support by phone and they said there was something wrong whit the new firmware. The backhaull is not functioning, the advice was to wait for the new firmware. There is still no new firmware. Is there another sollution to solf the problem?
Abke Please check your wired devices. What devices do you have connected to the LAN ports? It seems that this firmware has issues to handle certain wired devices.
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.
https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-and-connection-problems-Skybell/m-p/1649275/highlight/true#M43001
Abke wrote:
i bought the system and had to upgrade the firmware. Now i cant connect the satellite there is no responce at all. I had contact with support by phone and they said there was something wrong whit the new firmware. The backhaull is not functioning, the advice was to wait for the new firmware. There is still no new firmware. Is there another sollution to solf the problem?
Not a surprise.... I can sit and literally watch the status page of the Satellite change from 2.4Ghz to 5Ghz to no Ghz. Ironically, when I hit the reply to this post button just now, the satellite, which I'm hard wired to, cut out and went dark. It then bounced back on, then off, then on.
This is clearly a technical problem in firmware of the Orbi. The thing wasn't cheap either. We use it in our cabin in the mountains. In our house, we have Ubiquiti, and I have zero problems with it that are of consequence.
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#M4241630 feet is recommended in between them to begin with depending upon building materials. So try running the router along and see if the problem continues. And sure Daisy Chain IS check marked.
nanohead wrote:
Not a surprise.... I can sit and literally watch the status page of the Satellite change from 2.4Ghz to 5Ghz to no Ghz. Ironically, when I hit the reply to this post button just now, the satellite, which I'm hard wired to, cut out and went dark. It then bounced back on, then off, then on.
This is clearly a technical problem in firmware of the Orbi. The thing wasn't cheap either. We use it in our cabin in the mountains. In our house, we have Ubiquiti, and I have zero problems with it that are of consequence.
