projects / mech_eap.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f4637fe) | patch
Clear next_scan_freqs on wpa_supplicant FLUSH command
authorJouni Malinen <j@w1.fi>
Sat, 27 Dec 2014 13:37:13 +0000 (15:37 +0200)
committerJouni Malinen <j@w1.fi>
Mon, 29 Dec 2014 13:49:05 +0000 (15:49 +0200)
commitb8db1dfc5ca85b3443dab7757853b68687921d8e
tree1be680d8336cb3726349a16b9f796e2dc028d0fetree | snapshot
parentf4637fe0fd7f4b4b0cd0f1a4e48ccc94e944e160commit | diff
Clear next_scan_freqs on wpa_supplicant FLUSH command

It was possible for old scan state to remain from a previous test case
when an operation like WNM neighbor scan or another-BSS-in-ESS was
started, but stopped at the end of a test case. This could result in
failures, e.g., when running wnm_bss_tm_req followed by scan_setband.

Signed-off-by: Jouni Malinen <j@w1.fi>
wpa_supplicant/ctrl_iface.c diff | blob | history
Moonshot GSS-API mechanism