On Mon, Jan 13, 2020 at 12:37:31PM +0100, Markus Theil wrote: > In preparation for rx over nl80211 control port, this series adds > support for pre-auth handling. nl80211 control port rx forwards all EAPOL > and pre-auth frames over a nl socket if activated. Why would EAPOL RX over nl80211 control port need RSN preauthentication frames to use that same port? That does not sound like a reasonable constraint to me taken into account completely different protocol rules for EAPOL and RSN preauthentication frames. > driver: add rsn pre-auth rx event > nl80211: differentiate between ETH_P_PAE and ETH_P_RSN_PREAUTH for > control port rx > wpa_supplicant: add support for pre-auth rx over driver event > hostapd: add support for pre-auth rx over driver event There would need to be pretty strong justification for accepting these.. In other words, I'm dropping these now and I'd like to get the EAPOL RX over nl80211 control port working first before considering any changes to RSN preauthentication frames. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
