wpa_supplicant && associates to unknown AP

[Sam Leffler]

Matthias Apitz wrote:
> El día Sunday, March 01, 2009 a las 09:44:05AM -0800, Sam Leffler escribió:
>
>   
>> I don't see a wpa_supplicant log.  The way iwi works is rather a hack 
>> but necessitated by the crappy intel firmware.  There is no way to get 
>> iwi to just scan but not associate so what's done is we install an 
>> "impossible ssid" when we just want to scan then fill in the ssid and 
>> tell it to scan on just the channel where the desired ap is located.  
>> This has always worked but perhaps you caught ifconfig reporting status 
>> that was temporary.  Without logs it's impossible to tell.
>>     
>
> I will try to collect a wpa_supplicant log; this is a bit tricky because
> wpa_supplicant is launched at boot time with hardcoded flags in
> /etc/rc.d/wpa_supplicant and it seems it does not log via syslog (at
> least I don't see how this could be enabled in the man page);
>   

The no logging is because syslogd is started too late by rc.d.  I've 
brought this up (the ordering is complicated) but haven't had time to 
fix it myself.

To add -d you should be able to just add

wpa_supplicant_flags="-s -d"

in rc.conf.  This will work if you manually start things with

/etc/rc.d/netif start ath0

(or similar).

>   
>> The other possibillity is your wpa_supplicant.conf file allowed 
>> association to a "wildcard ap".  Can't tell w/o seeing the config file 
>> and/or log.
>>     
>
> No, there is no "wildcard ap".
>
> Thx for your reply in any case.
>
> 	matthias
>
>