From owner-freebsd-current@FreeBSD.ORG Thu Jun 16 20:11:48 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1DC916A41C for ; Thu, 16 Jun 2005 20:11:48 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72B1143D49 for ; Thu, 16 Jun 2005 20:11:48 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.94] ([66.127.85.94]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j5GKBlms016281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jun 2005 13:11:48 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <42B1DD17.3000601@errno.com> Date: Thu, 16 Jun 2005 13:12:07 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: James Snow References: <20050616191450.GA98695@teardrop.org> <42B1D9D9.7040604@errno.com> <20050616200450.GB98695@teardrop.org> In-Reply-To: <20050616200450.GB98695@teardrop.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: WPA Supplicant doesn't see my SSIDs? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2005 20:11:48 -0000 James Snow wrote: > On Thu, Jun 16, 2005 at 12:58:17PM -0700, Sam Leffler wrote: > >>What does ifconfig ath0 list scan show? > > > SSID BSSID CHAN RATE S:N INT CAPS > 0... 00:0e:83:af:77:f5 40 54M 27:0 100 EP WPA WME > 0... 00:0e:38:51:ca:6c 52 54M 28:0 100 EP WPA WME > 0x000000000... 00:07:eb:30:c6:de 1 11M 27:0 100 EPS > SDC-WAP-001 00:0f:66:18:20:00 6 11M 7:0 100 E > > My Windows box confirms that 00:0e:83:af:77:f5 is on channel 40, so > there's definitely some communication taking place. Are these ap's hiding their ssid? Logs from the kernel with scan debug enabled would be useful. I thought the probe request frames were sent with a directed ssid in them but the current scanning code is kinda stupid in this area. I've totally rewritten it but that won't go in 6.0. Sam