ioctl[SIOCSIWENCODEEXT]: Invalid argument

Vladimir Botka vbotka
Wed Jul 28 13:40:45 PDT 2010


On Tue, 27 Jul 2010 18:19:40 -0700
Dan Williams <dcbw at redhat.com> wrote:

> > > > in openSUSE 11.3, kernel 2.6.34, wpa_supplicant reports
> > > > "ioctl[SIOCSIWENCODEEXT]" [3] when used with ipw2200
> > > > [2] driver and WEP. For the record I've opened bug on [1].
> > > > Disabling 802.11w didn't help. Any idea ?
> > > > [1] http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2236
> > > 
> > > It depends on what parameter wpa_supplicant is trying to set, and
> > > what options are sent with that parameter.  If there's a chance
> > > you can change and rebuild your wpa_supplicant, we can figure out
> > > what that is. What configuration are you using?  Can you include
> > > the "-dddt" logs from the supplicant so that we can see what the
> > > supplicant is trying to do?
> > > 
> > I'm using configuration [1]. Please find attached
> > wpa_supplicant.log. Process was started from the command-line [2].
> > I'm not able to find reason why the "Association request " failed
> > [3].
> 
> Probably because if the driver fails to set the key, the supplicant
> shortens the time limit for association because the driver is probably
> going to fail the assocaition request anyway.
> 
> > MAC before disassociation [4] looks bad.
> 
> That's how WEXT (the old kernel wireless API) signals a disassociation
> event, or a failure to associate event:  all zeros.  Thats how we know
> that the driver failed to talk to the AP.
> 
> I'm having some trouble duplicating your problem, but I'm able to get
> associated with wpa_supplicant 0.6.8 and kernel 2.6.33.6 and kernel
> 2.6.34.1.  However, wpa_supplicant git does not work correctly for
> some reason.
> 
> Try this:
> 
> rmmod ipw2200
> modprobe ipw2200 debug=0xFFFFFFFF
> 
> and then let the supplicant run until you get a disassociation event
> or two, then kill it, then reply with the 'dmesg' output so we can
> see what the driver thinks its doing.

I've upgraded to the wpa_supplicant 0.7.2 . The problems remained the
same as in 0.7.1 . I keep running 0.7.2 now.

Thank you for the explanation. Please find attached messages with the
ipw2200 debug [1]. I think the corresponding parts of filtered messages
and wpa_supplicant.log are [2] and [3].

[1] options ipw2200 hwcrypto=0 led=1 debug=0xffffffff

[2]
Jul 28 09:50:23 dhcp38 kernel:[  468.763127] ipw2200: I
ipw_rx_notification disassociated:'vlado-test-ap1' 00:18:f3:98:d1:9e 

[3]
2010.07.28 09:50:23 Association request to the driver failed

Thank you,

	-vlado
-------------- next part --------------
A non-text attachment was scrubbed...
Name: messages1.tar.bz2
Type: application/x-bzip
Size: 5920 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20100728/1d70bdc3/attachment.bin 



More information about the Hostap mailing list