Got the error "Driver did not support SIOCSIWENCODEEXT" when trying WPS

Wed Apr 15 23:07:57 PDT 2009

All,

I resovled the issue by deleting the wpa_supplicant carried within Fedora
10. Thank you!

2009/4/15 Wuhua Xu <xu.wuhua at gmail.com>

> I would like to explain that I have an ath9k car and an ath5k card, and
> above test is runing on an ath5k card. Please let me know whether the
> "Wireless event" is the root cause.
> I paste a complete debug message here:
> 1239816402.418024: Associated to a new BSS: BSSID=06:23:cd:01:39:8e
> 1239816402.418027: No keys have been configured - skip key clearing
> 1239816402.418044: Associated with 06:23:cd:01:39:8e
> 1239816402.418046: CTRL_IFACE monitor send - hexdump(len=21): 2f 74 6d 70
> 2f 77 70 61 5f 63 74 72 6c 5f 33 36 39 31 2d 33 00
> 1239816402.418058: WPA: Association event - clear replay counter
> 1239816402.418061: WPA: Clear old PTK
> 1239816402.418062: EAPOL: External notification - portEnabled=0
> 1239816402.418065: EAPOL: External notification - portValid=0
> 1239816402.418066: EAPOL: External notification - portEnabled=1
> 1239816402.418068: EAPOL: SUPP_PAE entering state CONNECTING
> 1239816402.418070: EAPOL: enable timer tick
> 1239816402.418073: EAPOL: SUPP_BE entering state IDLE
> 1239816402.418075: EAP: EAP entering state INITIALIZE
> 1239816402.418077: EAP: EAP entering state IDLE
> 1239816402.418080: Setting authentication timeout: 10 sec 0 usec
> 1239816402.418084: Cancelling scan request
> 1239816402.418088: RTM_NEWLINK: operstate=0 ifi_flags=0x11003
> ([UP][LOWER_UP])
> 1239816402.418091: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
> 1239816402.418212: RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> 1239816402.418215: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
> 1239816402.418217: Wireless event: cmd=0x8b15 len=20
> 1239816402.418219: Wireless event: new AP: 00:00:00:00:00:00
> 1239816402.418225: Setting scan request: 0 sec 100000 usec
> 1239816402.418229: Added BSSID 06:23:cd:01:39:8e into blacklist
> 1239816402.418236: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> 1239816402.418238: CTRL_IFACE monitor send - hexdump(len=21): 2f 74 6d 70
> 2f 77 70 61 5f 63 74 72 6c 5f 33 36 39 31 2d 33 00
> 1239816402.418249: wpa_driver_nl80211_set_key: alg=0 addr=0x80b0316
> key_idx=0 set_tx=0 seq_len=0 key_len=0
> 1239816402.418713: nl80211: set_key failed; err=-2
> 1239816402.418716: wpa_driver_nl80211_set_key: alg=0 addr=0x80b0316
> key_idx=1 set_tx=0 seq_len=0 key_len=0
> 1239816402.418732: nl80211: set_key failed; err=-2
> 1239816402.418734: wpa_driver_nl80211_set_key: alg=0 addr=0x80b0316
> key_idx=2 set_tx=0 seq_len=0 key_len=0
> 1239816402.418746: nl80211: set_key failed; err=-2
> 1239816402.418749: wpa_driver_nl80211_set_key: alg=0 addr=0x80b0316
> key_idx=3 set_tx=0 seq_len=0 key_len=0
> 1239816402.418761: nl80211: set_key failed; err=-2
> 1239816402.418763: wpa_driver_nl80211_set_key: alg=0 addr=0x9f81b94
> key_idx=0 set_tx=0 seq_len=0 key_len=0
> 1239816402.418767:    addr=06:23:cd:01:39:8e
> 1239816402.418778: nl80211: set_key failed; err=-2
> 1239816402.418780: State: ASSOCIATED -> DISCONNECTED
>
>
> 2009/4/15 Wuhua Xu <xu.wuhua at gmail.com>
>
>  I'm using ath5k and AR2413. With the option -D nl80211 the error message
>> disappeared, but I got another error:
>> After association, I always got a "Wireless event: new AP:
>> 00:00:00:00:00:00", and then I got EVENT_DISASSOC because of the driver
>> event handler. Is this the root cause of the failure?
>> Just before that I got the following messages:
>>  RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
>> RTM_NEWLINK: IFLA_IFNAME: Interface 'wlan0' added
>> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP][LOWER_UP])
>> RTM_NEWLINK: IFLA_IFNAME: Interface 'wlan0' added
>> When I use madwifi with Honma's patch, I get only the first two lines.
>>  RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
>> RTM_NEWLINK: IFLA_IFNAME: Interface 'wlan0' added
>>
>> 2009/4/10 Jouni Malinen <j at w1.fi>
>>
>>  On Thu, Apr 09, 2009 at 11:29:10AM +0800, Wuhua Xu wrote:
>>>
>>> > I got the error when trying to use WPS with my atheros AR5416 and the
>>> option
>>> > nohwcrypt=1.
>>> >
>>> > ioctl[SIOCSIWENCODEEXT]: No such file or directory
>>> > ...
>>> > Driver did not support SIOCSIWENCODEEXT
>>> > State: ASSOCIATED -> DISCONNECTED
>>> > Is it a blocking error? How to work around it?
>>>
>>> I don't think that this is an issue in this particular case. Association
>>> seems to go through fine, but the AP does not start any handshake after
>>> it. Which AP are you using? Would you be able to run a wireless sniffer
>>> to capture the frames exchanged between the AP and the client?
>>>
>>> --
>>> Jouni Malinen                                            PGP id EFC895FA
>>>  _______________________________________________
>>> HostAP mailing list
>>> HostAP at lists.shmoo.com
>>> http://lists.shmoo.com/mailman/listinfo/hostap
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20090416/55c6f0fb/attachment.htm 