Using a unique SSID for each band (2.4 GHz and 5 GHz) allows users to manually choose which band to connect to, optimizing performance based on the specific needs and capabilities of their devices. This separation aids in better network management, reduced interference, and improved troubleshooting. Additionally, it prevents devices from needing to perform a full authenticated roam between bands, which can enhance connectivity stability and reduce latency So let’s create a unique SSID per band but throw, hotspot 2.0 SSID per band in…
Setup the test
We will assign the following recognizable names to the networks: OpenRoaming-2-4Ghz, OpenRoaming-5Ghz, and OpenRoaming-6Ghz.
Please note, at Cisco WLC 9800 vode 17.9.5 ensure the 6Ghz band is enabled first. The RCOI fields need to be in the Main SSID when MBSSID is active, otherwise, it will not even get broadcasted correctly and picked up by the device.
Now even with the correct information elements visible in the beacon, shown on the right
My MacBook M2 and iPhone 15 Pro (here on the left) do not recognize the 6Ghz band SSID as a Passpoint 2.0-enabled network.
Workaround and break the unique SSID per band concept
One possible workaround is to Make “one” dual-band SSID with the name OpenRoaming-5-6Ghz and lift on via the 5ghz band using the inband discovery protocols RNR (802.11k):
Here you see my MacBook connecting just fine:
Behind the scenes, the MacBook was connecting to the 5Ghz hotspot 2.0 enabled network and roamed to the 6Ghz band, because it’s the same SSID name this works.
Conclusion
Use a unique SSID for each band until you start using Hotspot 2.0 networks. I tested this with two different wireless vendors and got the same result. If you have a single-band 6Ghz Hotspot 2.0-enabled network and can connect without issues using the same setup on Windows or Android, please send me a message on LinkedIn or email me.