Wi-Fi 7 in the wild: MLO works, band steering fights it

Wi-Fi 7 access points are now common enough in production that a pattern has emerged, and it is a configuration pattern rather than a hardware one.

What MLO is doing well

The headline claim for Multi-Link Operation was never peak throughput — it was reliability. A client holding simultaneous links on 5 and 6 GHz can lose one to interference, a DFS event or a wall without a roam, a reassociation or a DHCP renewal.

In practice that is exactly what it delivers. On a video call, the difference is between a moment of slightly degraded audio and a visible freeze. For anyone with a business case built on real-time traffic, this is the feature worth paying for.

What is undoing it

Aggressive band steering.

Band steering exists to push dual-band clients off 2.4 GHz. The logic, in most controller implementations, is to decide which band a client "should" be on and encourage it there. Applied to a multi-link client, that logic is fighting the point of the feature: a Wi-Fi 7 client is meant to be on more than one band at once.

Symptoms look like clients that connect at good rates but do not aggregate, latency that is no better than the Wi-Fi 6E deployment it replaced, and multi-link associations that collapse to single-link within seconds.

What to check

• Does your controller report multi-link associations distinctly from single-link ones? If it cannot show you, it probably cannot handle them well either.
• Is band steering set to its most aggressive mode? On a Wi-Fi 7 SSID, turn it down.
• Are minimum RSSI or client-steering thresholds forcing disassociation on one link?
• Are 5 and 6 GHz both enabled on the same SSID? MLO across bands requires it.

The 320 MHz footnote

Separately and predictably, 320 MHz channels remain a demonstration feature outside the United States. Where a regulator opened only the lower 500 MHz of 6 GHz, a single 320 MHz channel consumes most of the band. That is not a channel plan.