Robert L Cochran wrote:
> I can't speak authoritatively, but this is what the wpa_supplicant
> README says:
> 1) WPA-Personal (PSK) as home network and WPA-Enterprise with EAP-TLS as
> # allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group
> # home network; allow all valid ciphers
> psk="very secret passphrase"
> Notice it is suggesting fewer options than you are actually using. It
> doesn't have an ap_scan option. I'm a great fan of using the smallest
> number of options that actually does the job -- you want to keep it simple.
> Bob Cochran
Thanks, Bob. That's precisely what I started with. Many error messages :(.
I left out the ctrl_interface_group line because it didn't seem relevant
and when I put one in, it didn't do anything.
The ap_scan line tells wpa_supplicant to do the scanning instead of the
device driver. This got rid of some errors.
The pairwise=TKIP line is necessary because something else, I'm not sure
right now what (CCMP?), is the default. And the proto=WPA line seems
superfluous (with the key_mgmt=WPA-PSK line) but also seemed to improve
Basically what you see is the result of studying the README,
understanding only some of it, and gleaning bits and pieces from
whatever tutorials, forum postings, and such I could find via Google.
Unfortunately, much of what I found was in reference to the use of
wpa_supplicant with other cards, other drivers, and on other flavors of
Linux, particularly Debian-based distros.
That's why I posted to this list. Even though it's not particularly
about ndiswrapper, that's the driver that this has to interact with.