The problem is that in this mode only clients that support 802.11w will be able to connect. Try Transition mode to allow unsupported clients. Otherwise use WPA2.
I don't find the "WPA3 Transition Mode" option on the MR30.5. And 802.11w is keeping on Required for WPA3.
So, like @PhilipDAth saied "Lots of devices can't connect to WPA3 yet. WPA3 needs at least 12 more months to mature before it can be widely used."
I suggest you use WPA2 for now.
Lots of devices can't connect to WPA3 yet. WPA3 needs at least 12 more months to mature before it can be widely used.
Yes, but the specification points out the phone is support WPA3-enterprise secutiry.
And I can get WPA3-enterprise security on the same client by Cisco C9120AX AP with WLC.
So I guess it a compatibility issue or not with Meraki?
Windows 11 says it supports WPA3 - but it has a serious bug that causes machines to intermittently disconnect and then not be able to re-connnect. The fix is scheduled to be released in Aprl 2024.
My Samsung phone says it supports WPA3. I can only keep it connected for about 4 hours. Then it randomly disconnects, and I have to turn WiFi off and back on again to get it working.
Lots of things say they are WPA3 compliant. Doesn't mean they are bug free.
Thanks for the feedback.
But my customer informed that they can get WPA3-enterprise on their side.
I don't how to explain what's different between Meraki and Cisco with WLC.
There are no options like "auth key mgmt" can be selected in Meraki.
I don't know the default value is 802.1X-SHA1 or 802.1X-SHA2 when configure as WPA3 only.