Agreed on the roaming and thought of that too, but I can’t find any information that 802.11r adaptive is related to RADUIS without RADIUS server configured with 892.11x.
Do you need 802.11r or can you try disabling that?
Adam R MS | CISSP, CISM, VCP, MCITP, CCNP, ITILv3, CMNO If this was helpful click the Kudo button below If my reply solved your issue, please mark it as a solution.
@jdsilva I am guessing you haven't worked in large campus environments were users with laptops roam around site. Without 802.11r client devices are much more likely to hang onto an access port even though there might be one closer with much better signal and throughput.
@jdsilva 802.11R is related to wireless handover, I was suggesting that without it client devices make the decsion and often they hang onto accesspoints for longer than they should.
This is a common problem I have seen over the years. 802.11r is a feature to help reduce this.
In an education environment you need wireless handover to be as seamless as possible especially with a large campus. Unless you haven't updated firmware sinc the Krack attack was discovered I see no reason why you wouldn't use this feature.
Do you need 802.11r or can you try disabling that?
I have already tried disabling and the RADIUS messages stop. But why? 802.11r is helpful to have enabled.
I'm not sure what you're after since you know the cause of the messages... Either it's something to do with how the Meraki implements the tagging of the 802.11r messages, or 802.11r really does use a RADIUS message.
Do you need 802.11r or can you try disabling that?
I have already tried disabling and the RADIUS messages stop. But why? 802.11r is helpful to have enabled.
I'm not sure what you're after since you know the cause of the messages... Either it's something to do with how the Meraki implements the tagging of the 802.11r messages, or 802.11r really does use a RADIUS message.
I'm trying to understand why the RADIUS even messages are showing, and showing failed auth messages in Wireless Health>Failed Connections. Disabling 802.11r can make them stop, but from my research there is no connection between 802.11r and RADIUS servers. Even Meraki support can't figure out why (yet). From what I can tell, the devices are spinning on failed auth attemps, delaying their wifi connections. Sometimes it's very quick and not-noticeable, but other times it's minutes causing user frustration. Hope that helps.
Yes, packet capture (monitor mode) has been done and sent to Meraki support about a week ago for investigation. First line support sees the RADIUS related info, but doesn't know why. Here's a link to it.