Update V1.9.1.12 Netgear officially announcing 'Improvement in wireless connection Stability'

Gentlemen, and ladies, if there are some,

Orbi needs to work as designed. That means any “fix” that requires; a. Disabling MU-MINO, b. Disable Beamforming, c. Reduce your power, d. Unplug you Satellites, etc, etc.

This is NOT a “fix”.

If my car is not operating properly and the dealer or manufacture instructs me to disable half my cylinders, never use my AC, radio, or cruise control, etc, keep your RPMs under 3K and never drive faster than 40MPH. Well, I think you would all agree that I would be “complaining”. And asking for a refund.

What “I believe” is happening is the Orbi Algorithm is not working for “SOME”. Of course, it will work for some, and not others. WHY? Because there is no single magic Algorithm that works for every environment and client device.

Cisco, and many other commercial grade wireless systems usually have a central control station that manages all APs in a multiple AP environment. This control station monitors all connections and status of all APs. It will change channels of some APs depending on the APs location and nearby interference, it will steer clients to other APs based on that devices capability and the overall status of the APs grid. And it will do MANY other things to insure a proper, healthy, functional and stable WIFI experience. It does this dynamically because WIFI conditions are never the same though the day, week, month, etc. One minute it has 10 clients, and one hour later it has 40. One hour the client is close to AP node 1, then it shows its closer to AP node 2. If the device does not move itself to the better AP node, the control station will move it.

If I have an Algorithm that instructs;

“If” client connects to Orbi Sat using 5G radio, “and” its RSSI is -65 or better, “then” DO NOT STEER to 2G, or Orbi Router.

“If” client RSSI drops below -65 using 5G radio, “then” steer to Sat 2G radio.

“If” client RSSI is -65 or lower using Sat 2G radio, “then” steer to Orbi Router 2G radio, “only” if RSSI is -65 or greater using Router 2G radio.

If client RSSI is -40 or greater using router 2G radio, “then” steer to router 5G radio.

The above is a VERY simple Algorithm for example purposes.

I think Netgears’ Algorithm is broken, and they are “trying” to find the one Algorithm that works for EVERYONE.

I think Netgear is trying to prevent the Sat backhaul from becoming too congested. Hence, the Algorithm is bias to the router and attempts to steer clients to the router as much as possible.

The problem with any “bias” to the router, is modern devices that are not STUPID and can see the Sat having a much greater signal (-50 or better, compared to the current -70 it may have), and it switches to the Sat. But then, the Orbi Algorithm runs again and kicks the client back to the router. And the circle starts again. The client devices will “argue” and switch back to the Sat and Orbi will repeat this process again.

But, after a few bounces between the router and Sat. the client drops its connection. And this can be due to several reasons. Example; 1. The client MAC is now showing on both Sat and Router and the L2 switching doesn’t know what path to reach the device. 2. The Apple client code realizes it cannot maintain a consistent connection to the WIFI network and hence it gives up and DROPS because its tired of being kicked several times to different AP nodes. It wants to choose the AP node itself, so it says screw you Orbi.

Some devices are STUPID, and once they lock onto a BSSID AP Node, they stay. And if steering moves that device to another AP node, then it stays there. Some devices with bad and lazy code are perfect candidates for steering because they lack the intelligence to move to a better AP node. But newer devices with good code DO NOT like steering. They will go to WAR with it. But, the WIFI gods know this, so they created flags that APs can send to clients with “suggestions”. “Hey iPhone, I have this wonderful AP node with a much better signal, so why not try that.” The iPhone can choose to ignore it. If the iPhone has an existing data connection that must be maintained, it may choose to stay on the AP node it is using, and perhaps switch AP nodes once it goes back to idle. Example, Flash is on a WIFI Call. So, NO. I want to stay where I am at because switching may break the connection. I will move later. But if Orbi forces the move and STP and other network features are not used...Guess what...DROP...

Again, this is what I believe could be causing the problem, but it’s hard to prove because unlike EVERYONE else who makes Multi-AP platforms with steering and other advanced features. They let you see the Algorithm and change it. They let you disable and enable features that may, or may not, work for YOU. WHY? Because they know there is no one size, no single Algorithm, that WORKS FOR EVERYONE.