Clinic tablets receive Access-Accept from RADIUS, yet the 4-way handshake fails and no user-plane traffic flows. Conceptually, what should the municipal WLAN team investigate first among AKM issues?
Select an answer to reveal the explanation.
Short Explanation
RADIUS said “you’re good,” but the 4-way still face-planted—that’s usually the lock types not matching after the bouncer waved you through. Check AKM/cipher negotiation, not the thermostat or DNS trivia first.
Full Explanation
A successful RADIUS Access-Accept establishes authentication/authorization path results, but the subsequent 4-way handshake still must agree on AKM/cipher parameters and confirm keys. Failures at that stage commonly point to suite mismatches or related key-handshake problems rather than HVAC, DNS PTR scavenging, or captive-portal certificate bit length as the primary AKM explanation. Isolating post-AAA handshake failures keeps troubleshooting focused on RSN negotiation and key confirmation.