Failed connection - unspecified radio

Solved
AnM
Here to help

Failed connection - unspecified radio

Hello. 

Recently having problems with industrial tablets that are trying connect to wifi on locations. In logs i can see 

AnM_0-1732533400318.png

This is both on firmware 30.7 and 30.7.1. I have MR36 on locations. I can't seem to find any informations about this specific reason.  

I would be gratefull for any kind of tips/help. Thanks

1 Accepted Solution
PhilipDAth
Kind of a big deal
Kind of a big deal

WPA3 has terrible compatibility at this point in time.  Try using WPA2 instead.

 

If you want to use WPA3 setup a seperate SSID for it.

View solution in original post

5 Replies 5
GreenMan
Meraki Employee
Meraki Employee

Just to be clear - it doesn't say 'unspecified radio' - this event is being seen across two radios;   2.4 GHz (radio 0 [channel = 1]) and 5 GHz (radio 1 [channel = 36])

The reason is unspecified.

I would check whether those client devices of yours support WPA3.  This technology is usually associated with 6 GHz W-Fi 6E and later - and require specific client side support.   My guess - based purely on the radios mentioned here - is that the Meraki APs may not support 6 GHz either.

AnM
Here to help

Right now this specific SSID is set, as shown

AnM_0-1732552408522.png

So if i'm understanding it correctly it should work fine. Configuration wasn't changed since the date it was set first time. It was working in the past without any problems, but i can't pinpoint exact date, when it stopped working correctly.

PhilipDAth
Kind of a big deal
Kind of a big deal

WPA3 has terrible compatibility at this point in time.  Try using WPA2 instead.

 

If you want to use WPA3 setup a seperate SSID for it.

cmr
Kind of a big deal
Kind of a big deal

Echoing what @PhilipDAth said, WPA3 Transition Mode is useless and should be avoided at all costs.  WPA3-PSK is much better, but will still generate some issues particularly with Android devices in my experience.

If my answer solves your problem please click Accept as Solution so others can benefit from it.
AnM
Here to help

Yeah so in my case (these industrial tablets were with android 13), switching to wpa2 only solved the problem. Thanks

Get notified when there are additional replies to this discussion.