ioctl[SIOCSIWENCODEEXT]: Invalid argument ipw2200 (-Dwext) using wpa_supplicant on EAP-PEAP/MSCHAPv2 network

Pedro Ramalhais ramalhais at serrado.net
Mon Dec 5 07:29:35 EST 2005


Ricardo Cordeiro wrote:
> Hello,
> 
> I was trying to authenticate to a WEP protected, IEEE8021X - EAP-PEAP/MSCHAPv2 authenticated wireless LAN using wpa_supplicant-0.4.7.
> 
> The supplicant authenticates successfully, but fails to set the dynamic WEP key.
> 
> Besides wpa_supplicant, I have currently installed the following packages on a Gentoo GNU/Linux laptop:
> 
> wireless-tools-28_pre12 (28_pre10 doesn't work too)
> ieee80211-1.1.6
> ipw2200-1.0.8-r1
> ipw2200-firmware-2.4
> 
> I ran: wpa_supplicant -c/etc/wpa_supplicant.conf -ieth1 -dddd -Dwext
> 
> here's a paste of the conf file:
> 
> ------------------------------------------------------------------------------
> update_config=1
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=wheel
> eapol_version=1
> ap_scan=1
> fast_reauth=1
> 
> network={
>         ssid="e-U"
>         scan_ssid=1
>         mode=0
>         key_mgmt=IEEE8021X
>         eap=PEAP
> 
>         identity="xxxxxx at iscte.pt"
>         password="xxxxxxxx"
>         phase2="auth=MSCHAPV2"
> }
> ------------------------------------------------------------------------------
> 
> Here's the important part of the output:
> 
> ------------------------------------------------------------------------------
> EAP: EAP entering state SUCCESS
> CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
> CTRL_IFACE monitor send - hexdump(len=26): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 39 31 31 39 2d 35 30 37 31 00 00 00
> EAPOL: SUPP_BE entering state RECEIVE
> EAPOL: SUPP_BE entering state SUCCESS
> EAPOL: SUPP_BE entering state IDLE
> RX EAPOL from 00:0f:f7:5c:37:60
> RX EAPOL - hexdump(len=61): 01 03 00 39 01 00 0d 00 00 43 92 2f aa 21 fd 34 23 a0 e9 c4 f7 d2 a3 86 27 3f 13 d9 32 6b 83 01 1d 43 f5 8b e2 3d 1f cc e9 0d 83 c4 61 58 fe 06 f6 a6 56 5f 3c eb 4a 7f 69 a6 6c 33 90EAPOL: Received EAPOL-Key frame
> EAPOL: KEY_RX entering state KEY_RECEIVE
> EAPOL: processKey
> EAPOL: RX IEEE 802.1X ver=1 type=3 len=57 EAPOL-Key: type=1 key_length=13 key_index=0x1
> EAPOL: EAPOL-Key key signature verified
> EAPOL: Decrypted(RC4) key - hexdump(len=13): [REMOVED]
> EAPOL: Setting dynamic WEP key: broadcast keyidx 1 len 13
> wpa_driver_wext_set_key: alg=1 key_idx=1 set_tx=0 seq_len=0 key_len=13
> RX EAPOL from 00:0f:f7:5c:37:60
> RX EAPOL - hexdump(len=48): 01 03 00 2c 01 00 0d 00 00 43 92 2f aa 21 fe 9e b8 c8 0f 64 29 8d 71 8e b2 f7 84 4f 48 5f 9b 83 74 c3 67 88 91 c8 c2 8f d5 b3 f7 37 df db 40 35
> EAPOL: Received EAPOL-Key frame
> EAPOL: KEY_RX entering state KEY_RECEIVE
> EAPOL: processKey
> EAPOL: RX IEEE 802.1X ver=1 type=3 len=44 EAPOL-Key: type=1 key_length=13 key_index=0x83
> EAPOL: EAPOL-Key key signature verified
> EAPOL: using part of EAP keying material data encryption key - hexdump(len=13): [REMOVED]
> EAPOL: Setting dynamic WEP key: unicast keyidx 3 len 13
> wpa_driver_wext_set_key: alg=1 key_idx=3 set_tx=128 seq_len=0 key_len=13
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> Driver did not support SIOCSIWENCODEEXT
> EAPOL: Failed to set WEP key to the  driver.
> ------------------------------------------------------------------------------
> 
> If there anything wrong? Can I provide you any more information?
> 
> Thanks in advance for any help,
> Ricardo Cordeiro

The problem (IIRC) is that the ipw2200 driver checks the index of
non-broadcast WEP keys. I thought that it was already fixed in 1.0.8,
not sure. Anyway there's a patch that fixes the problem, just search in
the ipw2100-devel mailing list archives.

-- 
Pedro Ramalhais



More information about the HostAP mailing list