From owner-freebsd-current@FreeBSD.ORG Thu Jul 12 07:14:30 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EFC8616A421 for ; Thu, 12 Jul 2007 07:14:30 +0000 (UTC) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.150.166]) by mx1.freebsd.org (Postfix) with ESMTP id BFFD913C455 for ; Thu, 12 Jul 2007 07:14:30 +0000 (UTC) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id F283B8CA067; Thu, 12 Jul 2007 15:14:29 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id DC3868CA05E; Thu, 12 Jul 2007 15:14:29 +0800 (CST) Date: Thu, 12 Jul 2007 15:14:29 +0800 (CST) From: Tai-hwa Liang To: David Wolfskill In-Reply-To: <20070711172448.GA42994@bunrab.catwhisker.org> Message-ID: <07071215124918.11674@www.mmlab.cse.yzu.edu.tw> References: <20070711172448.GA42994@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: Oddity with an(4): Channel reported by ifconfig is wrong X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2007 07:14:31 -0000 On Wed, 11 Jul 2007, David Wolfskill wrote: [...] > an0: flags=8843 metric 0 mtu 1500 > ether 00:40:96:32:19:a9 > inet 172.17.1.1 netmask 0xffff0000 broadcast 172.17.255.255 > media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) > status: associated > ssid 1:lmdhw-net channel 5 (56992 Mhz Turbo) > stationname FreeBSD > authmode OPEN privacy ON deftxkey 1 txpowmax 0 rtsthreshold 0 > fragthreshold 0 bmiss 0 mcastrate 0 roaming DEVICE > g1-1(7.0-C)[4] > > As you see, the an0 NIC (a PCMCIA part) is the only one in use (as > the miniPCI wi0 still doesn't associate). > > I don't expect that this is a critical issue, but it could be confusing. Thanks for reporting, I happened to have an Aironet miniPCI. Will look into this later. -- Thanks, Tai-hwa Liang