OK, so it is important to understand that there are some misconceptions about how we interpret Multi-Link Operation. This is often conflated with WPA3, which can lead to problematic client behaviors regarding the AKMs used and the roaming requirements on a dedicated WPA3 SSID we see today in our 802.11 enterprises.
One of the biggest items I wanted to touch on, and that I saw break a lot of client devices, was the requirement for GCMP-256. With respect to the resources I have available for testing and from my experience, the main differences were seen between Apple and Samsung STA devices. Regarding the GCMP-256 cipher requirement, no matter the configuration or combination of AKMs used, the Samsung Galaxy S25+ worked flawlessly on dedicated WPA3-only, GCMP-256-only 6Ghz SSIDs with Protected Management Frames (PMF) enabled by default.
The 2024 MacBook Pro could not operate on a WPA3-only, GCMP-256-only and PMF enabled SSID. CCMP-128 (AES-128) must be configured on the SSID in conjunction with the above-mentioned ciphers for our client, in this case, to successfully associate. The effective approach is to allow two specific AKMs to accommodate the 2024 MacBook Pro, which, I suppose in terms of Wi-Fi 7 and WPA3 mandates, is now a legacy device. My Samsung S25+, purchased six months ago, has no issues with any RSN IE blend or combination available for configuration. That is a win for Samsung, but later-generation iPhones performed just as well as the S25+, so this appears to be resolved on more modern devices, though it is important to note.
Slide 1: WPA3 Personal Mode with 6Ghz radio only operation – (Reference mrncciew)
As we continue our migration toward 802.11bn (Wi-Fi 8), we should see some of these incompatibilities resolve through enhancements, defect remediation from chipset vendors and BUs, and additional 802.11 community channels. Personally, I did not observe clients roaming seamlessly between access points while operating in Multi-Link Operation and from what I witnessed and heard presented at Wireless LAN Professionals Conference (WLPC 2026) in Phoenix, AZ, is that no, it is not supported. The client station must tear down and re-establish its MLO session all over again each time a STA roam is invoked and associated to their new AP.
Support for AP-to-AP simultaneous transmit and receive was presented and discussed among some colleagues as to be expected in later ratifications such as Wi-Fi 8. At present, most clients and chipsets are only presenting Multi-Link Operation across the radios on a single access point and its associated BSSID. They are not aggregating or sharing bandwidth across links from different access points yet. It can be configured but this is in a RF chamber lab environment where engineering developments and patent testing take place. This capability will require additional time before it becomes commonly available.
Works Cited:
1. Slide 1. https://mrncciew.com/2026/02/20/why-is-wpa3-adoption-so-slow/
Leave a Reply