On Tue, Jan 16, 2024 at 01:42:58PM +0000, Bock, Harry wrote: > We are using a custom driver for QNX 7, based on driver_bsd. > It is a minimal ioctl-driven driver. Sure, two logs are attached - > one where the error 30 is seen in the log and the supplicant > considers it an error, and one with my patch. > Ah, that's good to know. I'm surprised I didn't find a reference to it originally, > but it's been there a long time. No, we not using mac80211; our > QNX network driver does not handle the comeback automatically. > > If it is more appropriate to do so, we could modify it, but I'm sure there are > other non-mac80211 drivers that could benefit from it. Would it be worth > adding a WPA_DRIVER_FLAG_* for it? Thinking about it, I don't see much > harm in adding this behavior to SME unconditionally- if the kernel driver > does support it, it will never make it to the supplicant, and if it does not, > the supplicant has fallback support? > > Your call. We are happy to maintain this patch on our side, > but figured it might be useful to someone else. Thanks, this makes more sense now. This seems to work fine with mac80211 drivers as well, i.e., the wpa_supplicant functionality is not used in those cases and it does not break any functionality. In fact, I was even able to test this with mac80211_hwsim by disabling the kernel side association comeback mechanism. I applied the patch with some cleanup. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
