From owner-freebsd-mobile@FreeBSD.ORG Mon Mar 2 08:02:32 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 28AC9106566B for ; Mon, 2 Mar 2009 08:02:32 +0000 (UTC) (envelope-from Matthias.Apitz@oclc.org) Received: from mail.pica.nl (mail.pica.nl [192.87.44.30]) by mx1.freebsd.org (Postfix) with ESMTP id A8FD88FC12 for ; Mon, 2 Mar 2009 08:02:31 +0000 (UTC) (envelope-from Matthias.Apitz@oclc.org) Received: from rebelion.Sisis.de ([10.0.1.29]) by mail.pica.nl with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Mar 2009 09:02:29 +0100 Received: (from guru@localhost) by rebelion.Sisis.de (8.14.2/8.13.8/Submit) id n2282SKM002284; Mon, 2 Mar 2009 09:02:28 +0100 (CET) (envelope-from matthias.apitz@oclc.org) X-Authentication-Warning: rebelion.Sisis.de: guru set sender to matthias.apitz@oclc.org using -f Date: Mon, 2 Mar 2009 09:02:28 +0100 From: Matthias Apitz To: Sam Leffler Message-ID: <20090302080228.GA1989@rebelion.Sisis.de> References: <20090301080310.GA3186@rebelion.Sisis.de> <49AAC965.1030903@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <49AAC965.1030903@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.0-STABLE (i386) X-OriginalArrivalTime: 02 Mar 2009 08:02:29.0733 (UTC) FILETIME=[3BD2F150:01C99B0D] 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 Reply-To: Matthias Apitz List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 08:02:32 -0000 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 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 -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/