aboutsummaryrefslogtreecommitdiffstats
path: root/tests/test-md4.c
diff options
context:
space:
mode:
authorJouni Malinen <j@w1.fi>2012-01-01 16:53:12 (GMT)
committerJouni Malinen <j@w1.fi>2012-01-01 16:55:58 (GMT)
commit3d9975d5b0da66584107e99eb3c418b13b485d60 (patch)
tree4100e2fb13d0b1706f98a208abf98e2efb7f6f9f /tests/test-md4.c
parent0be3542338892e5c1e51682d3d2f509aa7dbda42 (diff)
downloadhostap-3d9975d5b0da66584107e99eb3c418b13b485d60.zip
hostap-3d9975d5b0da66584107e99eb3c418b13b485d60.tar.gz
hostap-3d9975d5b0da66584107e99eb3c418b13b485d60.tar.bz2
Do not trigger fast reconnection on locally generated deauth/disassoc
The deauthentication and disassociation events from nl80211 were being processed identically regardless of whether the frame was generated by the local STA or the AP. This resulted in fast reconnection mechanism getting triggered even in the case where the disconnection was detected locally (e.g., due to beacon loss) while this was supposed to happen only in the case where the AP is sending an explicit Deauthentication or Disassociation frame with a specific reason code. Fix this by adding a new deauth/disassoc event variable to indicate whether the event was generated locally. Signed-hostap: Jouni Malinen <j@w1.fi>
Diffstat (limited to 'tests/test-md4.c')
0 files changed, 0 insertions, 0 deletions