From owner-freebsd-current@FreeBSD.ORG  Thu Jun 16 20:03:59 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 9A4BD16A41C
	for <freebsd-current@freebsd.org>; Thu, 16 Jun 2005 20:03:59 +0000 (GMT)
	(envelope-from snow@teardrop.org)
Received: from imladris.teardrop.org (imladris.teardrop.org [66.92.66.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 68D1943D4C
	for <freebsd-current@freebsd.org>; Thu, 16 Jun 2005 20:03:59 +0000 (GMT)
	(envelope-from snow@teardrop.org)
Received: by imladris.teardrop.org (Postfix, from userid 100)
	id DB9BDBF6AB; Thu, 16 Jun 2005 16:04:50 -0400 (EDT)
Date: Thu, 16 Jun 2005 16:04:50 -0400
From: James Snow <snow@teardrop.org>
To: Sam Leffler <sam@errno.com>
Message-ID: <20050616200450.GB98695@teardrop.org>
References: <20050616191450.GA98695@teardrop.org> <42B1D9D9.7040604@errno.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <42B1D9D9.7040604@errno.com>
User-Agent: Mutt/1.4.2.1i
X-Mailman-Approved-At: Fri, 17 Jun 2005 11:59:27 +0000
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2005 20:03:59 -0000

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.

> Try not setting scan_ssid in the network block; not sure that it does 
> anything useful.                                                      

I've tried it both ways. I believe it handles APs that don't respond to
broadcasts. It was unclear if these Aironet APs were or not. There's no
obvious setting for it in their configuration.

> Also you terminate the scan after one try; when a channel is crowded
> sometimes the first scan may not find all ap's on it.

I just did that for the sake of pasting the output. I've left it running
while tweaking configuration options and running 'wpa_cli reconfigure'
but I've never managed to get our SSID to appear in wpa_supplicant's
output. Odd that it picks up SDC-WAP-001 no problem.

> You can also build the 80211debug program in src/tools/tools/ath and
> do 80211debug scan to get debug msgs from kernel sent to the console.

Will do.


-Snow