Hi.
I'm having a certain amount of trouble getting wpa_supplicant (0.4.1) to
authenticate to our production network. The problem is that madwifi (In
both branches) Uses an average 9 seconds to scan all available AP in its
vicinity. Some select times, the scan completes in less than the
hardcoded 5 seconds ( In wpa_supplicant_scan_results in
wpa_supplicant.c:
if (selected) {
if (wpa_s->reassociate ||
memcmp(selected->bssid, wpa_s->bssid, ETH_ALEN) !=
0) {
if (wpa_supplicant_scard_init(wpa_s, ssid)) {
wpa_supplicant_req_scan(wpa_s, 10, 0);
return;
}
wpa_supplicant_associate(wpa_s, selected, ssid);
} else {
wpa_printf(MSG_DEBUG, "Already associated with
the "
"selected AP.");
}
rsn_preauth_scan_results(wpa_s, results, num);
} else {
wpa_printf(MSG_DEBUG, "No suitable AP found.");
wpa_supplicant_req_scan(wpa_s, 5, 0);
}
)
, the supplicant authenticates and the link sticks like a horsefly.
Problem is, this takes an average of 15 minutes.
This should of course not be a problem, but as long as the madwifi
driver defends its name so vigourosly, an option to enter the timeout
values in the config file would be appreciated.
Best Regards
--
Ragnar Nicolaysen, UiO