Wifi-Event for when initial 4-way completes?
greearb at candelatech.com
Wed Jun 7 09:10:37 PDT 2017
On 06/07/2017 12:25 AM, Wojciech Dubowik wrote:
> 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]",
> 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.
Thanks for the hint. How do you receive this? By leaving 'wpa_cli' running?
I am having my supplicant manage 64+ station vdevs...is there a way to make it
get events from all of them at once so that I don't need 64+ monitor processes?
> 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
>> 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?
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc http://www.candelatech.com
More information about the Hostap