![]() The sta2.scan() calls were performing full scan of all channels and reporting only the BSS entry that happened to be the first one in the wpa_supplicant list. This is problematic since it is possible that the target AP was not found and incorrect BSS was selected and used for setting scan_freq which made the connection fail. Furthermore, there is no need to use full scan for these test cases, so use a single channel scan instead. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com> |
||
---|---|---|
.. | ||
ap-mgmt-fuzzer | ||
eapol-fuzzer | ||
hwsim | ||
p2p-fuzzer | ||
remote | ||
wnm-fuzzer | ||
.gitignore | ||
Makefile | ||
test-aes.c | ||
test-asn1.c | ||
test-base64.c | ||
test-https.c | ||
test-list.c | ||
test-md4.c | ||
test-milenage.c | ||
test-rc4.c | ||
test-rsa-sig-ver.c | ||
test-sha1.c | ||
test-sha256.c | ||
test-x509.c | ||
test-x509v3.c | ||
test_x509v3_nist.sh | ||
test_x509v3_nist2.sh |