From owner-freebsd-mobile@FreeBSD.ORG Sat Apr 26 16:09:44 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2A2F37B401 for ; Sat, 26 Apr 2003 16:09:43 -0700 (PDT) Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80FEC43FBD for ; Sat, 26 Apr 2003 16:09:43 -0700 (PDT) (envelope-from DougB@freebsd.org) Received: from master.dougb.net (12-234-22-23.client.attbi.com[12.234.22.23]) by rwcrmhc53.attbi.com (rwcrmhc53) with SMTP id <200304262309430530019e59e>; Sat, 26 Apr 2003 23:09:43 +0000 Date: Sat, 26 Apr 2003 16:09:42 -0700 (PDT) From: Doug Barton To: "M. Warner Losh" In-Reply-To: <20030426.165418.47319280.imp@bsdimp.com> Message-ID: <20030426160815.H13476@znfgre.qbhto.arg> References: <20030425133754.C35038@12-234-22-23.pyvrag.nggov.pbz> <20030426150924.H13476@znfgre.qbhto.arg> <20030426.165418.47319280.imp@bsdimp.com> Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: mobile@freebsd.org Subject: Re: Script to automatically configure a wireless card based on ssid X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Apr 2003 23:09:44 -0000 On Sat, 26 Apr 2003, M. Warner Losh wrote: > In message: <20030426150924.H13476@znfgre.qbhto.arg> > Doug Barton writes: > : > Also, once associated, the card won't report other cards... > : > : I'm not 100% sure what you mean by this. Even when I saw the WLAN ssid, if > : I subsequently did 'ifconfig wi0 wepmode mixed' then it saw my actual AP, > : correct ssid, etc. > > wicontrol -l, when wi0 is associated, only lists the ap you are > associated with. Netstumbler, when you are assocaited, listens on > only one channel... Ok, gotcha. I was running netstumbler both with, and without my AP running. Actually, I started running netstumbler before I even got my AP working. :) But I'll be sure to run through another series of tests if I see this mysterious WLAN thing again, thanks. Doug -- This .signature sanitized for your protection