mowerm wrote:
> $ sudo wpa_cli > > ap_scan 0
Well, on my system, this yields:
Could not connect to wpa_supplicant - re-trying
Then, nothing happens until I press Ctrl-C. So this doesnt seem to be a fix for people who use network-manager to drive wpa_supplicant.
I'd also like to point out that THIS bug has initially been reported by an Intel Wifi user. It is NOT a specific atheros/madwifi issue!
mowerm wrote:
> $ sudo wpa_cli
> > ap_scan 0
Well, on my system, this yields:
Could not connect to wpa_supplicant - re-trying
Then, nothing happens until I press Ctrl-C.
So this doesnt seem to be a fix for people who use network-manager to drive wpa_supplicant.
I'd also like to point out that THIS bug has initially been reported by an Intel Wifi user. It is NOT a specific atheros/madwifi issue!