wpa_supplicant can t associate with ndiswrapper driver

pomard · 01-10-2010, 02:51 PM

System configuration:
Debian lenny 2.6.26-2-686
wifi dongle driven by ndiswrapper and the windows NT sis163u driver

My wifi works fine with without wpa_supplicant but when I try to launch it with wpa_supplicant all the system freeze with the generic wext driver. I have the to access the interfaces file from another system to bring it up again.
So I tried to use another driver, I built wpa_supplicant 0.6.9 with ndiswrapper driver support. The system does not hang but wpa_supplicant cant associate to my ap.
The configuration is basic:
ap_scan=2
network={
ssid="3Com"
key_mgmt=NONE
id_str="home"
}

the result of
wpa_supplicant -Dndiswrapper -iwlan0 -c/etc/network/wpa_supplicant/wpa_supplicant.conf -dd

Code:

Initializing interface 'wlan0' conf '/etc/network/wpa_supplicant/wpa_supplicant.conf' driver 'ndiswrapper' ctrl_interface 'wpa_ssid=3Com' bridge 'N/A'
Configuration file '/etc/network/wpa_supplicant/wpa_supplicant.conf' -> '/etc/network/wpa_supplicant/wpa_supplicant.conf'
Reading configuration file '/etc/network/wpa_supplicant/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ap_scan=2
Line: 3 - start of a new network block
ssid - hexdump_ascii(len=4):
     33 43 6f 6d                                       3Com            
key_mgmt: 0x4
id_str - hexdump_ascii(len=4):
     68 6f 6d 65                                       home            
Priority group 0
   id=0 ssid='3Com'
Initializing interface (2) 'wlan0'
Interface wlan0 set UP - waiting a second for the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:40:f4:f0:86:ab
Driver does not support WPA.
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Trying to associate with SSID '3Com'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=ForceAuthorized
EAPOL: disable timer tick
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID '3Com'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Association request to the driver failed
...

running with strace give me a lot of "operation not supported"... I suspect the sys163u driver to be incompatible with wpa_supplicant...

1. Why my system hangs with wext?
2. Why wpa_supplicant cant associate with ndiswrapper?

Tx for your help, I tried to activate debug on my ndiswrapper module but unsuccessfuly

andywebsdale · 01-10-2010, 03:02 PM

You could try sticking this in the config file:

proto=WPA2
key_mgmt=WPA-PSK
psk=”mypsk”

You shouldn't need to build wpa_supplicant, just use the deb.
Have a look at HOWTO: WPA2 under Ubuntu 5.10 with a WPC54G v3 (Broadcom)

Some people HAVE had trouble with WPA & this driver (on Win XP SP2 as well) - someone said go toSIS's download page for a working version. Might be worth trying ndiswrapper with a driver from there

nimnull22 · 01-10-2010, 03:03 PM

Quote:

Originally Posted by pomard

1. Why my system hangs with wext?
2. Why wpa_supplicant cant associate with ndiswrapper?

Tx for your help, I tried to activate debug on my ndiswrapper module but unsuccessfuly

Because from you log:

Code:

...
Own MAC address: 00:40:f4:f0:86:ab
Driver does not support WPA.
...

pomard · 01-10-2010, 03:18 PM

nimnull22:

I saw this message (WPA not supported) but dmesg show that WPA is supported

Code:

[ 5576.514107] ndiswrapper: driver sis163u (Silicon Integrated Systems Corp.(1.05.14),11/02/2005,5.1.1039.1050) loaded
[ 5578.384019] wlan0: ethernet device 00:40:f4:f0:86:ab using NDIS driver: sis163u, version: 0x1000000, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 0457:0163.F.conf
[ 5578.401594] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK

Whatever, even if WPA is not supported by sis163u windows driver it should go on with key_mgmt=NONE

andywebsdale:
I tried first the deb package provided for my distrib but it doesnt integrate the ndiswrapper and the wext bring my system in an unusable state.
I will try with WPA_PSK but i think that I have, first, to bring the first level (NONE) in a working state...

pomard · 01-12-2010, 09:12 PM

Quote:

1. Why my system hangs with wext?

Running wpa-supplicant with gdb shows that the function ioctl is guilty. Especially when it tries to set the authentication type and that whatever the type. I still do not understand why ndiswrapper (or sis163u windows driver?) crashes the system when ioctl call it with SIOCSIWAUTH. The worst is that sometimes with gdb, more rarely, directly, everything goes ok either in WEP mode or WPA mode.
So i commented out this function call and returned -1 and built the binary wpa_supplicant.

Code:

        if (ioctl(drv->ioctl_sock, SIOCSIWAUTH, &iwr) < 0)

It s not the solution but it can help people who are confronted to the same pb...

Now it s working in open wep mode.

Quote:

2. Why wpa_supplicant cant associate with ndiswrapper?

I did non investigate...