usb network adapter with ndiswrapper can't connect to wpa with wpa-supplicant

AceofSpades19 · 07-10-2007, 08:01 PM

Hi, I'm using Ubuntu 7.04 with a usb network adapter connected with ndiswrapper to connect to a wpa-encrypted network with wpa supplicant
$ sudo wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -Dndiswrapper -w
Trying to associate with 00:13:46:a3:e1:48 (SSID='default' freq=2462 MHz)
Association request to the driver failed
Authentication with 00:00:00:00:00:00 timed out.

my wpa config file

ctrl_interface=/var/run/wpa_supplicant
network={
ssid="default"
proto=WPA
key_mgmt=WPA-PSK
psk=random numbers and letters generated by wpa_passphrase
}

AceofSpades19 · 07-11-2007, 01:03 PM

does anyone know whats wrong?

Hangdog42 · 07-11-2007, 01:09 PM

You might try using the wext driver instead of the ndiswrapper driver (so -dndiswrapper would be -dwext).

AceofSpades19 · 07-11-2007, 02:22 PM

I don't think thats the problem

Hangdog42 · 07-11-2007, 02:31 PM

Quote:

Originally Posted by AceofSpades19

I don't think thats the problem

Care to provide a bit more of an explanation why?

AceofSpades19 · 07-11-2007, 05:18 PM

because the ndiswrapper driver works perfectly fine, I think it has to do with my config file or my command and ndiswrapper supposedly is supported by wpa_supplicant

Hangdog42 · 07-11-2007, 05:28 PM

Quote:

Originally Posted by AceofSpades19

because the ndiswrapper driver works perfectly fine, I think it has to do with my config file or my command and ndiswrapper supposedly is supported by wpa_supplicant

You might be confusing two things here. There is the ndiswrapper kernel module driver that actually makes the card function and then there is the wpa_supplicant ndiswrapper driver that you specify on the command line that starts wpa_supplicant. Two different pieces of software. It is the second one I am suggesting you replace with wext. Both the wpa_supplicant ndiswrapper and wext driver will supposedly work with the ndiswrapper kernel module, however the wext driver is more generic and may be better supported. So even if the problem is in your config file, wext may be a better option.

As for the config file, here is an example of an entry that I use that works:

Code:

network={
ssid="WPA_NETOWRK_SSID"
scan_ssid=1
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
psk="WPA_Passphrase"
priority=1
}

After starting wpa_supplicant you also could check your iwconfig output and see if the key has taken and the card associated with the access point. If it hasn't associated, have a look in your log files and see if wpa_supplicant is complaining.

AceofSpades19 · 07-11-2007, 05:47 PM

I see, I'll try that when I get a chance

elbadry · 03-30-2008, 05:13 PM

I had the very same problem and it was solved by Hangdog's suggestion of using wext instead of ndiswrapper

Thanks a zillion!!