From Meraki Support: "Hi, Currently, the workaround is applied to the MX, therefore this is why you most likely haven't had issues with MX 18.210. Would you like to test by removing the backend workaround to see if the issue is present in mx 18.210?"   I do not know what the workaround was about but now clients are authenticated with 802.1X. A little bit scare to remove it... ... View more

Perfect, thank you! ... View more

And for WPA3 192 bits? it is all up to the client? I've noticed iPhone works, Android not (talking about their quite recent OS). ... View more

Rephrasing: A win 10 laptop works with SSID PSK WPA3-ONLY (aka PERSONAL). It "does not work" with SSID WPA3-ONLY in 802.1X with custom RADIUS (aka ENTERPRISE) which means once connected it shows: WPA-2 ENTERPRISE. ... View more

You did mention the nic card but if it works with SSID PSK WPA3-ONLY (aka PERSONAL) and it does not work with SSID WPA3-ONLY in 802.1X with custom RADIUS (aka ENTERPRISE). ... View more

Same laptop works with WPA3-Personal. Once is using 802.1X it shows WPA2-ENTERPRISE. ... View more

Thanks, Holli69. MX 18.208.0.1 just disrupted the entire 802.1x infrastructure.... It looks OK with MX 18.210. ... View more