WPA - AP association Issue

[Bryan Kadzban]

On Mon, Oct 29, 2007 at 07:12:18AM -0400, Dan Williams wrote:
> > Received 777 bytes of scan results (3 BSSes)
> > Scan results: 3
> > AP count: 3
> > num_prio: 0
> > No suitable AP found.
> 
> This means that the scan results did not find an AP that wpa_supplicant
> considers useful.

And also, the "num_prio: 0" line means that wpa_supplicant had no valid
network blocks in the internal structures that it uses to store the
config file contents.  I'm not sure why this is, but I don't see any
error from the config-file parsing code in the output you posted.  I may
be able to give you another few debug lines to (hopefully) narrow it
down later today.

(It may easily help if you *don't* use any iw* program before starting
wpa_supplicant (other than the scan program that Dan is suggesting
below).  Specifically, you pasted in some command that looks like it's
setting a WEP key -- I have a feeling this may be part of the issue.
See if it helps to remove this command.)

> Can you provide output of 'iwlist ath0 scan' (hide BSSIDs if you wish)
> and tell us which AP you're trying to connect to?

I'm guessing here, but I think that based on the "num_prio: 0" output,
it won't matter what SSID is in the scan list.  Still, this would be
useful information.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20071029/d822d523/attachment.pgp