wpa_supplicant: It takes ~10 seconds to connect to a Hidden profile (scan_ssid=1)
Hahn, Maital
maitalm
Wed Jul 8 04:28:17 PDT 2015
Hello,
I found an issue in the following scenario:
I have one hidden profile (scan_ssid=1) defined in my conf file.
The supplicant performs Normal Scan before performing Sched Scan.
In the Normal Scan, it first scans for wildcard SSID, waits for 5 seconds, and then scans the profile's SSID.
So the connection to the profile takes ~10 seconds. This is a bad user experience.
Suggested solution:
In the Normal Scan, switch the order of the scans. Start with the profile's SSID and after 5 seconds scan for wildcard SSID.
This can be achieved by the following patch:
diff --git a/wpa_supplicant/wpa_supplicant.c b/wpa_supplicant/wpa_supplicant.c old mode 100644 new mode 100755 index 93f1625..e303300
--- a/wpa_supplicant/wpa_supplicant.c
+++ b/wpa_supplicant/wpa_supplicant.c
@@ -3295,7 +3295,7 @@ int wpa_supplicant_driver_init(struct wpa_supplicant *wpa_s)
wpa_drv_flush_pmkid(wpa_s);
wpa_s->prev_scan_ssid = WILDCARD_SSID_SCAN;
- wpa_s->prev_scan_wildcard = 0;
+ wpa_s->prev_scan_wildcard = 1;
if (wpa_supplicant_enabled_networks(wpa_s)) {
if (wpa_s->wpa_state == WPA_INTERFACE_DISABLED) {
Please let me know if this is acceptable.
Thanks,
Maital
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.shmoo.com/pipermail/hostap/attachments/20150708/642c782c/attachment.htm>
More information about the Hostap
mailing list