From owner-freebsd-mobile@FreeBSD.ORG Mon Mar 2 16:05:48 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A90B1065670 for ; Mon, 2 Mar 2009 16:05:48 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 3CEBB8FC27 for ; Mon, 2 Mar 2009 16:05:47 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n22G5loH070125 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Mar 2009 08:05:47 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <49AC03DB.3090608@freebsd.org> Date: Mon, 02 Mar 2009 08:05:47 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Matthias Apitz References: <20090301080310.GA3186@rebelion.Sisis.de> <49AAC965.1030903@freebsd.org> <20090302080228.GA1989@rebelion.Sisis.de> In-Reply-To: <20090302080228.GA1989@rebelion.Sisis.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-DCC-x.dcc-servers-Metrics: ebb.errno.com; whitelist Cc: freebsd-mobile@freebsd.org Subject: Re: wpa_supplicant && associates to unknown AP X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 16:05:49 -0000 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 > >