WPA - AP association Issue

Bryan Kadzban bryan at kadzban.is-a-geek.net
Tue Oct 23 18:22:15 EDT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

(Please keep the hostap list CC'ed, in case anyone else has anything to
contribute.)

Mr. Maloomnahi wrote:
> The WPA devices are associating with the AP with EAP or PSK settings,
> but the association gets cut off due to no keys being set.

No it doesn't.  The messages below are perfectly normal; they refer to
WEP keys.

> =======================
> Added interface ath0
> RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
> Wireless event: cmd=0x8b06 len=8
> Ignore event for foreign ifindex 2

This line, however, appears possibly-suspect.  I don't know where the
ifindex gets assigned, but if you only have one wireless NIC, then you
need to get wpa_supplicant running on your single wireless NIC.

(Either that, or ifindex 2 is actually ath0, and this message is only
here because of a race between the "adding interface" operation and the
"foreign ifindex" decision.  I'm not sure.)

> RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
> RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
> Wireless event: cmd=0x8b15 len=20
> Wireless event: new AP: 00:14:78:8f:5e:49

So far so good, I think.  Although I don't see anywhere that says
wpa_supplicant chose this AP (or for what reason); did you cut anything
out of this log?  Or is this the normal output of the wext driver?
Normally the scan results (at least) are dumped.

> State: DISCONNECTED -> ASSOCIATED
> wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
> WEXT: Operstate: linkmode=-1, operstate=5
> Associated to a new BSS: BSSID=00:14:78:8f:5e:49
> No keys have been configured - skip key clearing

As above, this refers to WEP keys, and doesn't affect anything.

> No network configuration found for the current AP

I bet this line is your problem.  You need to actually set up the config
file correctly (it has to refer to this AP's SSID, for instance, and the
other settings need to match as well), otherwise this AP will be
ignored.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHHnQWS5vET1Wea5wRA8hlAKDJFTdIz15C4kYan5zUZEzEi+szjwCgtUob
ifOYJbBdd7/7xfmQO1qp2Dw=
=+sHn
-----END PGP SIGNATURE-----



More information about the HostAP mailing list