WPA Association with wext versus hostap

Aric D. Blumer aric at sdgsystems.com
Thu May 31 11:23:36 EDT 2007


I didn't see anything relating to this problem in bugzilla, so I'd like
to bounce it off the list:

I have a D-Link DI-524 access point.  I am connecting to it with a
Prism-based AmbiCom WL1100C-CF 802.11b card.  This is with Linux kernel
version 2.6.15 on a PXA255-based handheld computer with wpa_supplicant
0.4.9.

If I do "wpa_supplicant  -d -D wext -i wlan0 -c
/etc/wpa_supplicant.conf" it associates with the DI-524 just fine. 
However, if I do "wpa_supplicant  -d -D hostap -i wlan0 -c
/etc/wpa_supplicant.conf" it will not associate.  That last bit of info
I see is:

wpa_driver_hostap_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)


It then times out and tries again.

Anyone have any idea why the wext wap_supplicant driver would work, and
the hostap driver would not?

Thanks.



More information about the HostAP mailing list