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'm an IT consultant. I installed the RBK50 system over one year ago for a client. My client's video streaming became largely unusable around the time of the .210 release. I visited my client a few days ago. The wireless backhaul was "poor." I restarted the satellite and streaming worked fine again. By the evening, the problems started up again. After the satellite was unplugged, streaming worked fine again.
I noticed that after restarting the satellite, the ring turned magenta before it turned blue. I never recall it doing that before the .210 release.
Daniel_K wrote:
I'm an IT consultant. I installed the RBK50 system over one year ago for a client. My client's video streaming became largely unusable around the time of the .210 release. I visited my client a few days ago. The wireless backhaul was "poor." I restarted the satellite and streaming worked fine again. By the evening, the problems started up again. After the satellite was unplugged, streaming worked fine again.
I noticed that after restarting the satellite, the ring turned magenta before it turned blue. I never recall it doing that before the .210 release.
This software seems to have issues with some wired devices. If you have any mesh speakers (e.g. Sonos) wired to Orbi, please test to disconnect them and see if you will see improvements.
Wired Sonos seem to cause IP loops over time which will degrade the system performance and will consequently cause different "strange" issues.
I have used the instructions on post 105 on the link below to stop auto updating. Well, for the last 5 days anyway. Before when I rolled back the firmware, it auto updated immediately after connecting to the cable modem.
There are a couple of things to mention. There is a line orbi_auto_upg=0 in the OP. In my router it was set to =1. I didn't notice it at first, and my router updated even after setting the other lines to =0. I found another post that mentioned this, so be sure to set this like the others to =0 if it is not already. Also the line orbi_auto_upgrade may have a value greater than 1 when you start. Just set it to =0. Thirdly the OP says in step 6 not to put a space after "set". That did not work for me. I put a space in and the command worked.
Now when I log into the router I see a notice that there is new firmware, but it does not auto update. Hooray! My Carrier Infinity Touch thermostats are connecting again and I don't need an additional AP!
https://community.netgear.com/t5/Orbi/Firmware-V1-12-0-18-Discussion/td-p/1320421/page/5
Anyone else having issues with the VPN implementation? I have to keep disabling then re-enabling it to work. When it's "not working" I can still login to the VPN and access devices on my home network, but I can't connect to anything outside of it. I have the VPN set to "All sites on the Internet & Home Network" and when I enable the VPN server it will work for a few minutes, but then out of what seems like nowhere will kill the connection to the internet and give me only access to the home network. If I disable and re-enable the VPN then it works again for a bit.
Didn't have this problem before 2.2.1.210.
Also REALLY frustrating that the update was forced AGAIN. With this VPN issue and the fact that Netgear keeps forcing these updates, I'm really considering going back to my Amplifi system.
dkleinknecht wrote:
Anyone else having issues with the VPN implementation? I have to keep disabling then re-enabling it to work. When it's "not working" I can still login to the VPN and access devices on my home network, but I can't connect to anything outside of it. I have the VPN set to "All sites on the Internet & Home Network" and when I enable the VPN server it will work for a few minutes, but then out of what seems like nowhere will kill the connection to the internet and give me only access to the home network. If I disable and re-enable the VPN then it works again for a bit.
Didn't have this problem before 2.2.1.210.
Also REALLY frustrating that the update was forced AGAIN. With this VPN issue and the fact that Netgear keeps forcing these updates, I'm really considering going back to my Amplifi system.
When I first started using Orbi's VPN, I found that I had to check "all sites on the internet and home network" option AND re-download/re-apply the applicable OpenVPN config file to get it to work properly.
I also found that I had to enable guest network AND make the regular network visible to the guest network in order to access machines at home through the VPN.
I've tried all of this, I've even changed the ports and re-enabled VPN then downloaded the new profiles to use, same problem.
This only started happening after the latest forced updated, was fine on the previous version. It's really frustrating.
The auto-update of firmware 2.2.1.210 bricked my router. Fortunately a manual TFTP load of the firmware got it back up and running. This firmware version has caused major internet connectivity issues. All wired and wireless devices lose internet connectivity for several minutes, multiple times a day. It is not my ISP or any of the associated hardware.
Have you tried to disable the Auto Update on the Orbi?
sufus wrote:
The auto-update of firmware 2.2.1.210 bricked my router. Fortunately a manual TFTP load of the firmware got it back up and running. This firmware version has caused major internet connectivity issues. All wired and wireless devices lose internet connectivity for several minutes, multiple times a day. It is not my ISP or any of the associated hardware.
I have similar issues with you guys. I had auto update on, and after updating, it started to be unstable. I never check my router but these days, connections are unstable. Sometimes, signal is there on the client but there's no bandwidth because the satellites backhaul isn't good. Network map changes from green to yellow and yellow to green. Keeps fluctuating.
Has anyone experienced sudden problems with "unable to connect to network" after the update?
Extremely annoying and the kids are complaining as it is affecting their school work. Just as well I have a secondary wifi network system as backup......never trusting fully these relatively new stuff in the market
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:
https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-released-as-of-10-3-18/m-p/1647303/highlight/true#M42416
sycshk wrote:
I have similar issues with you guys. I had auto update on, and after updating, it started to be unstable. I never check my router but these days, connections are unstable. Sometimes, signal is there on the client but there's no bandwidth because the satellites backhaul isn't good. Network map changes from green to yellow and yellow to green. Keeps fluctuating.
My experience with this firmware is pretty much the same as every version before it. Half-finished, buggy, and unstable. For example:
- Still zero ability to program/tune QOS.
- Wired backhaul connections are still less stable than a $19 switch.
- Satellite booting up while router boots locks up the admin console.
And even with major problems still out in the field, Netgear won't allow owners to open a ticket without paying for extended support. Since I spent $350, I'm going to suffer with it as long as I can. But Orbi will be the last Netgear product I buy.What is the Mfr and model# of the ISP modem the NG router is connected too?
Is the Orbi system operating in Router or AP mode?
What is the Mfr and model# of the ethernet switch if one is in the configuration.
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.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. This would be effecting wired back haul configurations.
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#M42416For wired back haul:
Set up IP address reservations for each satellite and devices on the router as you add them to the router. The satellites need to be set up via wireless first. Then connect 1 satellite at a time to the ethernet LAN cable. Wait 5 minutes and the top led on the satellite should turn on BLUE. Set up an IP address reservation for the 1st satellite. Continue to do the same thing for the 2nd satellite. Then follow up with your devices.
OrbiPhilip wrote:
My experience with this firmware is pretty much the same as every version before it. Half-finished, buggy, and unstable. For example:
- Still zero ability to program/tune QOS.
- Wired backhaul connections are still less stable than a $19 switch.
- Satellite booting up while router boots locks up the admin console.
And even with major problems still out in the field, Netgear won't allow owners to open a ticket without paying for extended support. Since I spent $350, I'm going to suffer with it as long as I can. But Orbi will be the last Netgear product I buy.Please do not ignore my post and regurgitate a boilerplate list of questions. You are cluttering up the forum and aren't helping anyone.
My Orbi Pro 2.2.1.210 experience so far.
1. First, version 204 was very solid, with no obvious problems causing WIFI, Internet or other disruptions.
2. Orbi Product RBS50Y is still running build 204. Why has Netgear not yet updated this product? All other Orbi Pro (SRR60 and SRS60) devices are using 210.
3. I am now suffering several “new” problems. Google Assistance devices, Apple TV devices, and IP Cameras are now showing continued “disconnects” several times per day.
4. A very strange problem I have yet to fully diagnose and find root cause is; Devices at times obtain an IP address that is not part of any DHCP scope I use with my THIRD-PARTY Sophos router. I use a small DHCP Scope 192.168.0.50-100/24. However, I use DHCP reservations for all my “known” devices. It is CRITICAL that each device receive the specific IP address I assigned via reservations, as the Sophos Router (Firewall) uses specific firewall security groups/rules to control what the devices(s) can do. If any devices use an IP address that is NOT the designated reserved IP, the devices will fail to function. Forcing me to investigate WHY, only to discovery it “somehow” obtained an IP address that is WITHIN the 192.168.0.x/24 subnet…BUT….is not the proper reserved IP. Now I scratch my head and wonder….WHO IS YOUR DHCP SERVER, which many IOT devices do not show. So, now I must find time to investigate this problem WHICH DID NOT EXIST prior to version 210. I suspect Orbi is running a DHCP server within its topology, ALTHOUGH I am running AP MODE….As everyone knows, the first DHCP server to respond..WINS…..So I ask Netgear to send this to your dev team and confirm “Does Orbi run a DHCP service, even when using AP Mode, and if the answer is YES…WHY?” And, before anyone ask “why not use static IPs”…I have many good reason. 1. I have 60+ devices and static IP management can be difficult. 2. Many devices are made CHEAP and will not last more than 2 years. It is very painful to change an IP camera or other IOT device and jump through the loops of reconfiguring its interface. DHCP gives me the EASY task of simply changing the MAC address in my scope and having a guarantee of the IP address. This method is also being used within MANY corporate environments today. I love my DHCP solution, and prior to Orbi Pro version 210…NEVER HAD ANY PROBLEMS!!!
5. I also observe Daisy Chain mode working against itself. There are times I observe a satellite choosing to use another satellite for uplink. But within MINUTES all satellites will prefer the router, and never look back to a satellite. This DOES impact speed performance. I have a satellite which is MUCH CLOSER to another Satellite that has an ethernet backhaul connection. And when the satellite uses the other satellite (via daisy chain)…I observe speeds between 400-600Mbps….But when the satellite is “FORCED” to go back to the main router (which is further)….speeds drop to 200-400….It is my expressed opinion that Netgear needs to loosen the stranglehold on satellites being force to the router.
Conclusion, so far I wish I could role back to 204…but we ALL KNOW Netgear Orbi will autoupdate back to 210 minutes later. Version 210 is the ONLY version that FINALLY allows the disabling of autoupdate.
And finally, still no vLAN support in AP Mode, still no ability to seperate BSSIDs for 2 and 5Ghz bands. Still not QoS for AP mode CoS tagging, still no SNMP to better monitoring Obi devices, and still no features that Make Orbi Pro anything close to a “business product”.
And still “SILENCE” from Netgear.
If you still have the v204 files you could go back...and block the auto update.
Orbi does not and will not support seperating of SSIDs between the radios. It's based on using Smart Connect and a MESH system. It's how NG intended Orbi to work.
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. NG is aware of this.
Flash008 wrote:
My Orbi Pro 2.2.1.210 experience so far.
1. First, version 204 was very solid, with no obvious problems causing WIFI, Internet or other disruptions.
2. Orbi Product RBS50Y is still running build 204. Why has Netgear not yet updated this product? All other Orbi Pro (SRR60 and SRS60) devices are using 210.
3. I am now suffering several “new” problems. Google Assistance devices, Apple TV devices, and IP Cameras are now showing continued “disconnects” several times per day.
4. A very strange problem I have yet to fully diagnose and find root cause is; Devices at times obtain an IP address that is not part of any DHCP scope I use with my THIRD-PARTY Sophos router. I use a small DHCP Scope 192.168.0.50-100/24. However, I use DHCP reservations for all my “known” devices. It is CRITICAL that each device receive the specific IP address I assigned via reservations, as the Sophos Router (Firewall) uses specific firewall security groups/rules to control what the devices(s) can do. If any devices use an IP address that is NOT the designated reserved IP, the devices will fail to function. Forcing me to investigate WHY, only to discovery it “somehow” obtained an IP address that is WITHIN the 192.168.0.x/24 subnet…BUT….is not the proper reserved IP. Now I scratch my head and wonder….WHO IS YOUR DHCP SERVER, which many IOT devices do not show. So, now I must find time to investigate this problem WHICH DID NOT EXIST prior to version 210. I suspect Orbi is running a DHCP server within its topology, ALTHOUGH I am running AP MODE….As everyone knows, the first DHCP server to respond..WINS…..So I ask Netgear to send this to your dev team and confirm “Does Orbi run a DHCP service, even when using AP Mode, and if the answer is YES…WHY?” And, before anyone ask “why not use static IPs”…I have many good reason. 1. I have 60+ devices and static IP management can be difficult. 2. Many devices are made CHEAP and will not last more than 2 years. It is very painful to change an IP camera or other IOT device and jump through the loops of reconfiguring its interface. DHCP gives me the EASY task of simply changing the MAC address in my scope and having a guarantee of the IP address. This method is also being used within MANY corporate environments today. I love my DHCP solution, and prior to Orbi Pro version 210…NEVER HAD ANY PROBLEMS!!!
5. I also observe Daisy Chain mode working against itself. There are times I observe a satellite choosing to use another satellite for uplink. But within MINUTES all satellites will prefer the router, and never look back to a satellite. This DOES impact speed performance. I have a satellite which is MUCH CLOSER to another Satellite that has an ethernet backhaul connection. And when the satellite uses the other satellite (via daisy chain)…I observe speeds between 400-600Mbps….But when the satellite is “FORCED” to go back to the main router (which is further)….speeds drop to 200-400….It is my expressed opinion that Netgear needs to loosen the stranglehold on satellites being force to the router.
Conclusion, so far I wish I could role back to 204…but we ALL KNOW Netgear Orbi will autoupdate back to 210 minutes later. Version 210 is the ONLY version that FINALLY allows the disabling of autoupdate.
And finally, still no vLAN support in AP Mode, still no ability to seperate BSSIDs for 2 and 5Ghz bands. Still not QoS for AP mode CoS tagging, still no SNMP to better monitoring Obi devices, and still no features that Make Orbi Pro anything close to a “business product”.
And still “SILENCE” from Netgear.
Following on from previous posts in this threads I thought I'd update on my issues that are still apparent despite a factory reset.
I was seeing internet dropouts (both WiFi and wired) approximately once a day. Removing the wired bachaul and going back to wireless has completely cured this. I have had zero dropouts in the 10 days or so since I did this.
Following a factory reset I still have the following issues:
- Philips Hue issues are back with Routines simply not activating/deactivating.
- Momentary WiFi dropouts are still seen on my iPad when connected to the satellite i.e. the iPad drops the WiFi symbol and there's no connectivity. It comes back after a few seconds.
Anybody knows, when they plan to release another firmware?
The .210 is simply crap... It's the first time I have major issues with Orbi (RBR40) since buying it half a year ago. Since two weeks my satellite (RBW30) has poor performance, although I didn't change any settings.
Tried downgrading (worked fine, but than there's the annoying auto-update), factory reset. Watching anything on the TV is a no go...
If they don't fix this soon, I'll probably need to sell the Orbi, as it's useluess for me now.
NG doesn't post when new FW will be forth coming.
You can try to block autoupdate:
Azel80 wrote:
Anybody knows, when they plan to release another firmware?
The .210 is simply crap... It's the first time I have major issues with Orbi (RBR40) since buying it half a year ago. Since two weeks my satellite (RBW30) has poor performance, although I didn't change any settings.
Tried downgrading (worked fine, but than there's the annoying auto-update), factory reset. Watching anything on the TV is a no go...
If they don't fix this soon, I'll probably need to sell the Orbi, as it's useluess for me now.
- For Orbi Pro customers,
They need to provide a time frame. ASAP!!’
I have worked in I.T. For 20 years.
ALL tech business product makers understand they must communicate and provide status of problem resolution.
Anything less and business customers take their money else where.
Another reason business product makers DO NOT force software updates on their customers.
NETGEAR OWES A SPEEDY FIRMWARE UPDATE FOR ORBI PRO CUSTOMERS WITH “fixes” TO THESE PROBLEMS.
Or, a rollback in the update servers! Allowing us to go back to 204 and not be “forcefully” updated back to 210.
Or, a 204 build repackage for build 210. Simply slipstream the 204 code into 210.
Netgear has options to fix this TODAY, and their “choice” to not fix this today or this weekend should speak LOUDLY to all Netgear customers.
Configuration:
(ISP) ROGERS 1GB -> (ROUTER/MODEM) CODA-4582U 2a -> ORBI
Problem: Unable to get stable 600mbit+ connection via CAT6e network cable when connected to ORBI. If connected directly to CODA-4582U 2a, then I get stable 950mbit+ speed is achieved.
For testing i have utilized fast.com & speedtest.net
Things attempted when troubleshooting:
1) Upgraded to latest firmware V2.2.1.210 and performed factory reset. (NO DIFFERENCE)
2) Downgraded firmware to V2.1.2.18 and factory reset (No difference)
3) Modified CODA-4582U 2a settings from bridge mode to router, and Orbi as Access point. (with this method i wanted to minimize the load on orbi with firewall, dhcp and other items disabled) (NO DIFFERENCE)
4) Disabled IPV6 on CODA-4582U 2a (NO DIFFERENCE)
5) Introduced cisco switch in between CODA-4582U 2a and orbi (NO DIFFERENCE) 6) QoS page seems broken/not designed for newer version of bootstrap/css/html. I attempted to delete all, /QOS_rule.htm, enable/disable via http://orbilogin.com/QOS_main.htm (NO DIFFERENCE)
Basically, my Orbi us unusable. Tried EVERY one of the hairbrained setting changes suggested here over and over and over. Completely useless.
The thing worked fine in my small cabin for the past year, now it is completely unreliable. The router seems to be functioning most of the time, but the satellite is now FUBAR. Wired, wireless, 2.4ghz, 5ghz, doesn't matter. its on, off, up down, poor, disconnected, orange, blue, white, etc all by itself.
Its a shame, as the packaging of the Orbi is convenient, but the device is garbage now because of this fabulous "Update".......
I think I may upgrade to Ubiquiti.....
Download version 2.1.1.16 for both the router and satellite.
https://community.netgear.com/t5/Orbi/Orbi-RBK50-firmware-V2-2-1-210-update-slows-WAN-speed-with-30-to/m-p/1651159/highlight/true#M43338You'll need to block the auto updater.
nanohead wrote:
Basically, my Orbi us unusable. Tried EVERY one of the hairbrained setting changes suggested here over and over and over. Completely useless.
The thing worked fine in my small cabin for the past year, now it is completely unreliable. The router seems to be functioning most of the time, but the satellite is now FUBAR. Wired, wireless, 2.4ghz, 5ghz, doesn't matter. its on, off, up down, poor, disconnected, orange, blue, white, etc all by itself.
Its a shame, as the packaging of the Orbi is convenient, but the device is garbage now because of this fabulous "Update".......
I think I may upgrade to Ubiquiti.....
Quick update for anyone who might be interested.
My last attempt to get this firmware to work was to lower the RTS/CTS, first to 1500, then to 500. No luck. At this point I give up: .210 is junk and I've downgraded & disabled auto-updates.
To anyone frustrated with this firmware, I highly recommend you do the same.
Also:
- ignore suggestions around daisy chaining, it's irrelevant unless you have more than 1 satellite. Anyone suggesting this has no clue.
- RTS/CTS tweaking does not seem to help at all, YMMV but I spent a few weeks trying and monitoring the results, no luck. (See previous post for some of the data.)
