Hello Ben,
I have been using this part of wpa_supplicant to notify that 4-Way
handshake is completed.
around line 868 in wpa_supplicant.c
#if defined(CONFIG_CTRL_IFACE) || !defined(CONFIG_NO_STDOUT_DEBUG)
wpa_msg(wpa_s, MSG_INFO, WPA_EVENT_CONNECTED "-
Connection to "
MACSTR " completed [id=%d id_str=%s%s]",
MAC2STR(wpa_s->bssid),
ssid ? ssid->id : -1,
ssid && ssid->id_str ? ssid->id_str : "",
fils_hlp_sent ? " FILS_HLP_SENT" : "");
#endif /* CONFIG_CTRL_IFACE || !CONFIG_NO_STDOUT_DEBUG */
You can pack whatever notification message inside the if statement.
Br,
Wojtek
On 07/06/17 02:46, 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?
Thanks,
Ben
