GWTechTalk
Occasional Visitor
I believe there’s currently nothing that can be done to address Broadcom-related errors or issues with Multi-Link Operation (MLO), as these are proprietary to Broadcom. That said, I own the same router and, in my experience, there is no tangible advantage to using MLO over simply enabling a 320 MHz channel width on the 6 GHz band.
MLO operates by splitting traffic—one connection for upload and another for download. However, there are no consumer-grade adapters on the market today that can handle more than two simultaneous connections, not unless you wish to spend $300-$600 only on a Wi-Fi adapter. I recommend disabling 2.4 GHz as an available MLO band. The biggest issue I’ve noticed is that MLO can actually reduce performance. One direction (either upload or download) often underperforms, creating an imbalance. For example, your device might be downloading over 6 GHz at 320 MHz and achieving speeds around 1.8 Gbps at 25 feet. But if upload is routed through the 5 GHz band at 160 MHz, your connection might show an estimated 2 Gbps link speed—yet, real-world throughput drops to around 1 Gbps or less due to overhead.
In my opinion, MLO is not ready for widespread use. I suspect that each MLO link is not operating in half-duplex mode, effectively cutting the available bandwidth in half still. I also believe the advertised performance claims are misleading, especially when encryption overhead is factored in—though I haven’t yet tested this specifically.
There has been some discussion about eventually allowing any band and any channel width to participate in MLO. If that becomes possible, we could potentially see two separate 6 GHz connections each using 320 MHz, which might allow a 2x2 client to achieve a full 5 Gbps in both directions. That would be a game-changer.
Lastly, don’t rely too heavily on your device’s reported link speeds. In practice, you’ll typically get about half of the estimated throughput. If you want a more accurate measure, check your router’s wireless logging page. It displays real-time bandwidth allocation per client—but again, expect to see only about half of those numbers in real-world use.
Last edited:
Different logic now, living with different subnet at the moment. Also had to delete and reconfigure it because clients were no longer able to associate over night without changes, reboot didn't fix it. No idea why, but now the missing checkbox for main network access is available (deleted the network before without success, still a bit flakey obviously, at least on my AX86Upro).
