+ hostap list
On 6/7/2017 2:46 AM, Ben Greear wrote:
I have been tracking down a nasty EAPOL related bug in ath10k, and found
something that may be peripheral, or maybe
it is significant.
My logic is basically to kick supplicant, watch 'iw events', and then
when I see something
like "sta62 (phy #5): connected to 00:0e:8e:f8:73:96", I consider it
connected and start
dhcpd.
But, it appears that the 'connected' message comes out before the EAPOL
4-way completes, so
I am starting dhclient before the encryption is really set up properly.
At best, this slows
things down and makes dhclient have to retry.
Is there some existing event or state I can probe to determine when the
initial 4-way is complete?
In case there is not, maybe that event would be worth adding?
Or, should I hack on supplicant instead and grab the info out of it
somehow?
The completion of the 4-way handshake is a supplicant state. Reaching
that state the PTK is set in the driver. It fires a CTRL-EVENT to the
wpa_s control interface. Actually found a python script eapol_test.py in
hostap repo that catches that event. So you may check it out.
Gr. AvS
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
