From owner-freebsd-mobile@FreeBSD.ORG Sat Apr 26 10:02:48 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 7F46537B401; Sat, 26 Apr 2003 10:02:48 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E27A43FA3; Sat, 26 Apr 2003 10:02:47 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h3QH2kA7067824; Sat, 26 Apr 2003 11:02:46 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 26 Apr 2003 11:02:31 -0600 (MDT) Message-Id: <20030426.110231.99254364.imp@bsdimp.com> To: DougB@freebsd.org From: "M. Warner Losh" In-Reply-To: <20030425133754.C35038@12-234-22-23.pyvrag.nggov.pbz> References: <20030424.195012.00542650.imp@bsdimp.com> <20030425133754.C35038@12-234-22-23.pyvrag.nggov.pbz> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: mobile@freebsd.org cc: mtm@identd.net 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 17:02:48 -0000 In message: <20030425133754.C35038@12-234-22-23.pyvrag.nggov.pbz> Doug Barton writes: : On Thu, 24 Apr 2003, M. Warner Losh wrote: : : > In message: : > John Baldwin writes: : > : > status: associated : > : > ssid WLAN 1:WLAN : > : > stationname "FreeBSD WaveLAN/IEEE node" : > : > channel 11 authmode OPEN powersavemode CAM powersavesleep 100 : > : > wepmode OFF weptxkey 1 : > : : > : Well, it claims to be associated, which is odd. I don't actually check : > : the ssid except for matching up wepkeys. Instead, I check the status : > : which is 'associated' in this case. : : John, you're correct of course, sorry. I should have double-checked the : code again before I posted. I had "associated + ssid" merged in my brain, : which your code does a better job of distinguishing. : : > : If there really isn't an AP, then that's : > : a bug that should be addressed. : > : > We don't use WLAN internally for anything. So there MUST be a WLAN : > around that you don't know about... : : Yeah, I actually grep'ed our code for 'WLAN,' and of course didn't find : anything. According to netstumbler mine is the only AP in action within : radio range. I'm not disagreeing with you, just stating the source of my : contention. :) Is it possible that this is something specific to the : netgear card? How would I go about confirming that this is a real AP or : not? The other thing that I should try of course is to take the laptop : elsewhere, which I will at my earliest convenience. What does wicontrol -l tell you? Are you doing something like ifconfig wi0 ssid WLAN did you? Also, once associated, the card won't report other cards... Warner