Failed to set encryption with wpa_supplicant failed to connectAP

Bryan Kadzban bryan at
Fri Dec 30 13:03:54 EST 2005

Haydar Tekir wrote:
> ap_scan=2

Have you tried anything else for ap_scan?  I believe a lot of drivers
don't support it; I'm fairly sure that only the ndiswrapper or Windows
NDIS drivers are supposed to work with it.  I believe most of the
testing on Linux happens with ap_scan=1 (or whichever value is the

> RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
> Trying to associate with SSID 'mesiah'
> <...>
> <...>
> Wireless event: cmd=0x8b06 len=8
> Wireless event: cmd=0x8b1a len=19

These two events (from some cursory Google research) are "set frequency"
and "set SSID".  No surprise there -- that's what ap_scan=2 does.  It
runs through each of the network blocks in the config file, and tries to
associate with each, in turn...


But "something" (not sure what) comes back and disconnects.

I'm thinking the driver (and when I say "driver", I don't really know if
the problem is with the -Dwext code inside wpa_supplicant, or the Linux
wireless extensions interface inside the ipw2100 kernel module) doesn't
support ap_scan=2.  If you don't need =2, try ap_scan=1.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : 

More information about the HostAP mailing list