Date: Sat, 26 Apr 2003 16:09:42 -0700 (PDT) From: Doug Barton <DougB@FreeBSD.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: mobile@freebsd.org Subject: Re: Script to automatically configure a wireless card based on ssid Message-ID: <20030426160815.H13476@znfgre.qbhto.arg> In-Reply-To: <20030426.165418.47319280.imp@bsdimp.com> References: <20030425133754.C35038@12-234-22-23.pyvrag.nggov.pbz> <20030426150924.H13476@znfgre.qbhto.arg> <20030426.165418.47319280.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 26 Apr 2003, M. Warner Losh wrote:
> In message: <20030426150924.H13476@znfgre.qbhto.arg>
> Doug Barton <DougB@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030426160815.H13476>