On 26-4-2017 9:20, Johannes Berg wrote: > On Tue, 2017-04-25 at 20:56 +0200, Arend Van Spriel wrote: >> >> You might, but not about this ;-) The other approach I had in mind is >> to only pass the flag for drivers with 4-way-hs support. In that case >> wpa_supp also has to check that to determine whether the flag should >> be taken into account. Assuming the driver supporting 4-way-hs can >> provide the port state info. Otherwise, a new ext_feature flag would >> be needed. > > I think it's reasonable to assume 4-way-HS offload drivers can support > it. I tested the 4-way-hs (both Personal and 802.1X) with boolean parameter similar to what is proposed in the patch for roaming "cfg80211/nl80211: add authorized flag to roaming event" and it works fine. So I can extend it for use in connect result. Just had one issue regarding the type, ie. flag vs. u8 because of how things are done in wpa_supplicant supporting QCA roam+auth vendor-specific event. Regards, Arend
