A city employee SSID capture shows EAP Request Identity looping and…

Question

A city employee SSID capture shows EAP Request Identity looping and the TLS tunnel never establishing. What is the best protocol-analysis conclusion?

Accepted Answer

The 802.1X/EAP exchange is stalling at identity or TLS setup—investigate client identity response, EAP method, or RADIUS path rather than RF coverage alone. — If the door keep asking 'who’s there?' and never hears an answer, you don’t resurvey the parking lot—you fix the name tag and the guard desk. An EAP Identity loop is that stuck greeting before the TLS tunnel even starts.

Answer

Identity loops always mean the AP channel width is 160 MHz and must be forced to 20 MHz.

Answer

EAP Request Identity frames are multicast Beacons; looping them is normal on every secure SSID.

Answer

TLS never runs over EAP, so the capture must be filtered incorrectly for DHCP only.

A city employee SSID capture shows EAP Request Identity looping and the TLS tunnel never establishing. What is the best protocol-analysis conclusion?

Short Explanation

Full Explanation