From owner-freebsd-mobile@FreeBSD.ORG Fri Apr 25 13:44:57 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 EA6AF37B401; Fri, 25 Apr 2003 13:44:57 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36F1743FE3; Fri, 25 Apr 2003 13:44:57 -0700 (PDT) (envelope-from DougB@freebsd.org) Received: from 12-234-22-23.client.attbi.com ([12.234.22.23]) by rwcrmhc52.attbi.com (rwcrmhc52) with SMTP id <2003042520445605200nsapke>; Fri, 25 Apr 2003 20:44:56 +0000 Date: Fri, 25 Apr 2003 13:44:55 -0700 (PDT) From: Doug Barton To: "M. Warner Losh" In-Reply-To: <20030424.195012.00542650.imp@bsdimp.com> Message-ID: <20030425133754.C35038@12-234-22-23.pyvrag.nggov.pbz> References: <20030423223710.P7551@znfgre.qbhto.arg> <20030424.195012.00542650.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 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: Fri, 25 Apr 2003 20:44:58 -0000 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. Doug -- This .signature sanitized for your protection