WPA-PSK locks up at 4WAY_HANDSHAKE (2/4) / setting: ndiswrapper, ubuntu, WG511 (v1)

Sebastian Eiser sebastian.eiser at gmail.com
Tue Mar 14 14:37:16 EST 2006


Guys, you're wonderful!

I just tried your suggestions (but I couldnt get the AP log - my
neighbor is gone).

right, Bryan first
> What kernel version is this?
2.6.12-9-686

> -Dwext instead of -Dndiswrapper

same problem with
> SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
but additional:
> Driver does not support WPA.
and it seems to me that it wouldnt work: it fails already in state ASSOCIATING.

thanks so far! do I need addional setup before using the wext driver?

seb

terminal output:
-----
seb at ubuntu-seb:~$ sudo wpa_supplicant -i wlan0 -D wext -c
/etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
Line: 17 - start of a new network block
ssid - hexdump_ascii(len=7):
     57 47 2d 4e 65 74 7a                              WG-Netz
scan_ssid=1 (0x1)
proto: 0x1
key_mgmt: 0x2
PSK - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='WG-Netz'
Initializing interface (2) 'wlan0'
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
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
ioctl[SIOCSIWPMKSA]: No such device
SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
Own MAC address: 00:09:5b:45:df:68
wpa_driver_wext_set_wpa
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWAUTH]: No such device
Driver does not support WPA.
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such device
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
wpa_driver_wext_set_countermeasures
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
wpa_driver_wext_set_drop_unencrypted
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWAUTH]: No such device
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
Wireless event: cmd=0x8b2a len=12
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=7):
     57 47 2d 4e 65 74 7a                              WG-Netz
Scan timeout - try to get results
Received 2484 bytes of scan results (10 BSSes)
Scan results: 10
Selecting BSS from priority group 0
0: 00:04:0e:7e:49:32 ssid='WG-Netz' wpa_ie_len=26 rsn_ie_len=0 caps=0x11
   selected
Trying to associate with 00:04:0e:7e:49:32 (SSID='WG-Netz' freq=2447 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WEXT auth param 6 value 0x1 - ioctl[SIOCSIWAUTH]: No such device
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=26): dd 18 00 50 f2 01 01 00 00 50 f2
02 01 00 00 50 f2 02 01 00 00 50 f2 02 00 00
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00
00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWAUTH]: No such device
State: SCANNING -> ASSOCIATING
wpa_driver_wext_associate
ioctl[SIOCSIWGENIE]: No such device
WEXT auth param 0 value 0x2 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 1 value 0x4 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 2 value 0x4 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 3 value 0x2 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 10 value 0x1 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 8 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
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=Auto
Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b04 len=12
Wireless event: cmd=0x8b1a len=19
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING




On 3/14/06, Bryan Kadzban <bryan at kadzban.is-a-geek.net> wrote:
> On Tue, Mar 14, 2006 at 01:56:29PM +0100, Sebastian Eiser wrote:
> > SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
>
> What kernel version is this?  It might work better (especially if you're
> using the latest ndiswrapper) to use the wext driver in wpa_supplicant
> instead of the ndiswrapper driver.  (-Dwext instead of -Dndiswrapper)
>
> > and in the end:
> > WPA: Sending EAPOL-Key 2/4
> > >> all the time. It seems like the AP doesnt accept the key and
> > wouldnt let me connect. is there a way to check that in detail.
>
> Only if you can get at logs from the AP that would tell you why it's
> dropping the EAPOL-Key frame.  The most common reason is a mismatch in
> PSK values, but there are other reasons too.  I think looking into wext
> (assuming you have a new enough kernel) would be a bit more promising,
> though.
>
>
>
>



More information about the HostAP mailing list