[PATCH 1/3] AP: add station to driver before sending Assoc Resp
Sun Aug 2 11:24:03 PDT 2015
On Thu, Jul 09, 2015 at 02:26:24PM +0200, Michal Kazior wrote:
> Station could receive Assoc Resp from AP and start
> sending frames back (e.g. NullFunc saying it goes
> to sleep) to AP before the AP processed TX_STATUS
> for the Assoc Resp. Depending on device driver and
> event ordering the station could end up being
> Deauthenticated with reason 7 (class 3 from
> non-assoc sta) by the AP.
> + /* TODO: The station shouldn't be considered as Associated
> + * until after Assoc Resp ACK is delivered. However some
> + * drivers can get racy and end up deauthing stations before
> + * hostap adds the station entry.
> + *
> + * Currently stations are transitioned from non-existent into
> + * associated state right away. Ideally this should be split so
> + * that station can have 2 transitions: non-existent ->
> + * authenticated, authenticated -> associated.
> + */
I think it would be good to do this properly and implement that
not-associated -> associated transition in the kernel before changing
hostapd behavior here to create associated STA entries in the driver
before the STA is actually associated.
Jouni Malinen PGP id EFC895FA
More information about the Hostap