Hi Jouni, Johannes et al., On Wed, Feb 22, 2017 at 1:27 AM, Arend Van Spriel <arend.vanspriel@xxxxxxxxxxxx> wrote: > On 21-2-2017 13:37, Johannes Berg wrote: >> >>> What I am also missing is how to deal with NL80211_CMD_CONNECTED >>> event signalling. Should that be given after (un)successful >>> completion of the 4-way handshake or should we have a separate event >>> for that? >> >> That's a good point. I don't think a new event really works well, but >> perhaps we should extend the NL80211_TIMEOUT_* values with this? It's >> not strictly a timeout, I guess, but it's not a direct rejection of the >> association either. >> >> Any thoughts? > > I discussed about the event mechanism with Jithu which is who asked me > to look at their patches for this feature. His suggestion was to have a > "port authorized" event after successful handshake as it will help in > key mgmt offload cases. He gave the following example: Suppose you are > doing a fresh 8021x followed by 4way handshake offload. Right now there > is no event to indicate to the upper layer that the 4way handshake have > been completed successfully. So the only thing to do in wpa_supplicant > is to consider it completed and if not be hit with deauth. In wpa_supplicant terms, I was looking for an event notification to move the wpa_state from WPA_ASSOCIATED to WPA_COMPLETED. :) Thanks, -- Jithu Jance
