<br>When hostapd is running in 802.1x mode and an associated client (AP's perspective) sends ASSOC or RE-ASSOC, both are treated as RE-ASSOC by hostapd. With syslog logging level set to 0, the event sequence is as the following:
<br><br><font size="2"><a href="http://daemon.info">daemon.info</a> hostapd: wlan0: STA 00:12:f0:5b:95:2a IEEE 802.11: associated<br>daemon.debug hostapd: wlan0: STA 00:12:f0:5b:95:2a WPA: event 1 notification<br>daemon.debug
hostapd: wlan0: STA 00:12:f0:5b:95:2a WPA: event 4 notification<br><br>At this point, if the AP does not receive EAPOL-Start from the client (event 5 notification), for any reason, the connection remains "authorized" but there is no longer any KEY.
<br><br>In a real assoc event, hostapd will take the data path to immediately begin .1X authentication, so the connection can move along, whether STA sends EAPOL-Start or not.<br><br>It would be good if on a "re-assoc" event, hostapd does the same thing, without waiting for STA's EAPOL-Start to show up.
<br><br>This can be accomplished by adding "sta->eapol_sm->reAuthenticate = TRUE;" in the function ieee802_1x_new_station, in the else clause of "if (sta->pmksa)", just before stepping through the eapol state machine.
<br><br>-Ta<br><br></font>