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'...
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.
I don't remember if you have tried this or not:
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.
AC641 wrote:
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.
