On Wed, Apr 10, 2019 at 03:00:16PM +0000, Sergey Matyukevich wrote: > SAE connection fails if CSA occured during any previous connection > since the start of current wpa_supplicant runtime. > > The root cause is as follows. If STA channel changes due to CSA, > then bss->freq is updated in mlme_event_ch_switch. However this > value is not cleared between connections. So later it will be > used during SAE AUTH frame exchange. I'd guess this is referring to use of SAE authentication offload or some other special case since I don't see how bss->freq would have an impact of SAE authentication when using NL80211_CMD_AUTHENTICATE. > By the way, it looks like cleaning up bss->freq field would be a better > option. But so far I could not figure out a good place for this kind of > cleanup. Any suggestions are welcome. Yeah, I think I'll rather do that and also update bss->freq in station mode after association. Setting drv->first_bss->freq to 0 in nl80211_mark_disconnect() is likely going to handle most, if not all, the needed cases. If that does not fix this for your case, please share a wpa_supplicant debug log showing the exact sequence in which bss->freq ends up getting used to select incorrect channel for SAE authentication frames. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
