[hostap driver] not authenticating when used w/ wpa-supplicant / network-manager

[Dan Williams]

On Tue, 2007-08-14 at 08:51 -0600, Andrew Jorgensen wrote:
> Hello,  I am writing to get some information to help resolve this bug
> in Ubuntu: https://bugs.launchpad.net/bugs/125832
> 
> Please refer to that bug for more detail about the problem.  Basically
> wpa-supplicant reports something like the following when attempting to
> connect to an open, unencrypted network:

The driver is not able to associate with the network.  When doing this,
run "iwevent" and post the output.  If you're doing a plain
wpa_supplicant run with a minimal network block for an unencrypted
network, then the possibility the driver got borked exceeds the
possibility that wpa_supplicant is at fault, though it can't be ruled
out.

If there's any way to enable debugging of orinoco and get some debug
output as to _why_ the driver can't associate, that's the best thing to
do.  Some drivers are sensitive to the ordering of WEXT calls, others
are stupid and require iwpriv options to be called, etc.  The only thing
that's really useful in a situation like this is driver debug output.

Dan

> <2>Authentication with 00:00:00:00:00:00 timed out.
> <2>Trying to associate with 00:60:1d:1f:09:54 (SSID='onenet' freq=2412 MHz)
> <2>Authentication with 00:00:00:00:00:00 timed out.
> <2>Trying to associate with 00:60:1d:1f:09:4c (SSID='onenet' freq=2462 MHz)
> <2>Authentication with 00:00:00:00:00:00 timed out.
> <2>Trying to associate with 00:60:1d:1f:09:4c (SSID='onenet' freq=2462 MHz)
> <2>Authentication with 00:00:00:00:00:00 timed out.
> <2>Trying to associate with 00:60:1d:1f:19:62 (SSID='onenet' freq=2432 MHz)
> <2>Authentication with 00:00:00:00:00:00 timed out.
> <2>Trying to associate with 00:60:1d:1f:19:62 (SSID='onenet' freq=2432 MHz)
> <2>Authentication with 00:00:00:00:00:00 timed out.
> <2>Trying to associate with 00:60:1d:23:92:3f (SSID='onenet' freq=2437 MHz)
> 
> We're to the point now, though, where some cards work perfectly and
> other cards don't.  We have presumed that this may have something to
> do with the interaction between the driver and the firmware because
> the cards that don't work are card with older firmwares.
> 
> One card that works has
> NICID: id=0x800c v1.0.0 (PRISM II (2.5) PCMCIA (SST parallel flash))
> PRIID: id=0x0015 v1.1.1
> STAID: id=0x001f v1.8.0 (station firmware)
> 
> One that doesn't has
> NICID: id=0x8002 v1.0.0 (HWB3163-01,02,03,04 Rev A)
> PRIID: id=0x0015 v0.3.0
> STAID: id=0x001f v1.7.1 (station firmware)
> 
> That last one is, unless I'm mistaken, the latest firmware available
> for that revision hardware.
> 
> Our question is if wpa-supplicant is supposed to work only on cards
> with more recent firmwares or if there's really a bug here - and if
> there is a bug where do we go looking for it.
> 
> We're using Ubuntu's build of kernel 2.6.22
> (linux-image-2.6.22-9-generic) which doesn't appear to have any source
> code changes from what's in the kernel.
> 
> Thanks in advance for any help, and feel free to comment on the bug in
> launchpad if that's more appropriate.
> 
> - Andrew Jorgensen
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap