WPA failure with AR6000

Dan Williams dcbw
Thu Mar 13 09:25:07 PDT 2008

On Thu, 2008-03-13 at 08:57 -0700, William Hegardt wrote:
> Having trouble getting a new ARM based platform up and running that
> uses an AR6000 radio.
> WPA almost works but fails to complete and authentication seems to
> start over again.
> If anyone is willing to take a look and point me in the right
> direction towards solving this, I would be most appreciative.
> The supplicant driver interface is based on madwifi. I've tried
> supplicant versions 0.4.9, 0.5.10, and also 0.6.3 which generated the
> trace below.
> Here's my wpa_supplicant.conf file: 
> http://pastebin.com/m117cdc9
> Here's my .config file:
> http://pastebin.com/m2b531cde
> And here's the -ddd trace output from wpa_supplicant:
> http://pastebin.com/m6092415d
> Note that the AR6000 driver seems to generate a number of custom
> wireless events where the custom string points to unprintable data, so
> I modified driver_wext.c to not output the string in that case. I'm
> not sure if this indicates a serious problem or not.
> I also found that the trace output: ioctl[SIOCGIWAP]: Invalid argument
> is caused by the driver not having a connection at that point in time

Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:0d:ed:c3:02:1b
ioctl[SIOCGIWAP]: Invalid argument
Associated with 00:00:00:00:00:00

These are driver problems.  First, the driver says it's associated.  The
SIOCGIWAP event should _not_ fail here, it should be returning
00:00:00:00:00:00 if disconnected, or a valid BSSID if connected.  It
shouldn't be returning EINVAL if it's connected.  If it's _not_
connected, then it should have sent a disconnect event right when it
disconnected, which it doesn't appear to be doing.


More information about the Hostap mailing list