Skip to main content

EAP timing metric

Extensible Authentication Protocol timings are recorded and can be tracked over time

Tracking EAP timing can help to identify issues with 802.1X (i.e. RADIUS authentication) performance. This metric is only available for sensors/SSIDs that are using EAP authentication.

Find the sensor you wish to examine, and click through:

Looking at the WiFi panel, scroll down until you find the AP association time chart:

When you find it, click the + symbol to expand additional content:

The EAP time chart will appear:


The EAP time itself starts when the sensor's supplicant emits the first EAPOL START frame. The timer ends when the identity exchange is complete and the EAP SUCCESS frame is emitted.

The time focusses just on the EAP exchange, in the context of Wi-Fi 802.1x, the AP ASSOCIATION TIME, as seen above in the screenshot, accounts for the association request / response frame and the subsequent 4-way handshake that ensues.

In the context of an ethernet based 802.1x network, the EAP TIME measurement is the exact same, but the "NETWORK AUTHENTICATION TIME" represents the outerloop of the sensor's supplicant operation whilst the EAP TIME is just based on the emitted frames:

The UXI sensor makes use of the upstream, open source wpa_supplicant project which implements a 2s preamble delay as part of interface bootstrapping which is incorporated into the NETWORK AUTHENTICATION TIME metric. So for context of considering and evaluating ethernet 802.1x EAP response times, focus should be on the EAP TIME metric itself, not the authentication time.

Did this answer your question?