From owner-freebsd-current@FreeBSD.ORG Wed Aug 3 02:53:47 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41F7316A41F for ; Wed, 3 Aug 2005 02:53:47 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDE3843D45 for ; Wed, 3 Aug 2005 02:53:46 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.93] ([66.127.85.93]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j732rhms011688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Aug 2005 19:53:44 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <42F031E1.3080806@errno.com> Date: Tue, 02 Aug 2005 19:54:25 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: rnoland@2hip.net References: <1123020549.3017.32.camel@bbeng-laptop.acs.internap.com> In-Reply-To: <1123020549.3017.32.camel@bbeng-laptop.acs.internap.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: ath + wep issue 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: Wed, 03 Aug 2005 02:53:47 -0000 Robert C. Noland III wrote: > I am having an issue with static wep on my ath card, -current sources as > of this morning EST. It is a Linksys WPC55ag card. I also have an old > Netgear wi card that works shown at the bottom. > > ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) > ... > ath0: mem 0xf4010000-0xf401ffff irq 11 at device 0.0 on > cardbus0 > ath0: Ethernet address: 00:12:17:6e:fc:18 > ath0: mac 5.9 phy 4.3 radio 3.6 > > laptop# ifconfig ath0 ssid "test001" wepmode on weptxkey 1 wepkey "xxxx" > laptop# ifconfig ath0 up > > Tue Aug 2 17:27:19 RTM_IFINFO: if# 3, link: down, > flags: > Tue Aug 2 17:27:25 RTM_IEEE80211: scan complete > Tue Aug 2 17:27:25 RTM_IEEE80211: associate with 00:0d:93:e9:cf:d4 > Tue Aug 2 17:27:25 RTM_IFINFO: if# 3, link: up, > flags: > Tue Aug 2 17:27:25 RTM_IEEE80211: disassociate > Tue Aug 2 17:27:25 RTM_IFINFO: if# 3, link: down, > flags: You associated with the ap then fell off either because the ap dropped you or your station initiated it. The easiest way to see which is to enabling debugging; I prefer to use 80211debug from tools/tools/ath; e.g. 80211debug state+assoc or probably ifconfig ath0 debug will give you enough info. The output of 80211stats should also tell you what happened. > > The disassociate message concerns me, but it should work... > > ath0: flags=8843 mtu 1500 > inet6 fe80::212:17ff:fe6e:fc18%ath0 prefixlen 64 scopeid 0x3 > ether 00:12:17:6e:fc:18 > media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps) > status: no carrier > ssid test001 channel 1 > authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 46 > protmode CTS roaming DEVICE bintval 100 > > At this point, the card is no longer scanning and the lights on the card > continue blinking as if it is associated (slowly in sync, as opposed to > alternately blinking like mad when it is scanning) yet status shows no > carrier. dhclient will not work when the interface is in this state. > It seems to just broadcast and eventually die. > > wi0: at port 0xe000-0xe03f irq 11 > function 0 config 1 on pccard0 > wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163-SST-flash > wi0: Intersil Firmware: Primary (0.3.0), Station (1.3.4) > wi0: Ethernet address: 00:30:ab:07:e4:7b > > laptop# ifconfig wi0 ssid "test001" wepmode on weptxkey 1 wepkey "xxxx" > laptop# ifconfig wi0 up > > Tue Aug 2 17:35:57 RTM_IFANNOUNCE: if# 3, what: arrival > Tue Aug 2 17:39:06 RTM_IFINFO: if# 3, link: unknown, > flags: > Tue Aug 2 17:39:06 RTM_IEEE80211: disassociate > Tue Aug 2 17:39:06 RTM_IFINFO: if# 3, link: down, > flags: > > again with the disassociate message. This seems to force wpa_supplicant > to start scanning again, so I can't currently use wpa_supplicant on this > network. Actually, wpa_supplicant doesn't ever seem to be able to > associate on the wi card, but static configuration works. > wpa_supplicant on the ath card seems to associate, then catches the > disassociate and starts scanning again. lather, rinse, repeat... > > wi0: flags=8843 mtu 1500 > inet6 fe80::230:abff:fe07:e47b%wi0 prefixlen 64 scopeid 0x3 > ether 00:30:ab:07:e4:7b > media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) > status: associated > ssid test001 channel 1 bssid 00:0d:93:e9:cf:d4 > stationname "FreeBSD WaveLAN/IEEE node" > authmode OPEN privacy MIXED deftxkey 1 wepkey 1:104-bit txpowmax > 100 > bintval 100 > > dhclient does work here, and then I can start the vpn and roam about the > office... I've been testing ath w/ static key wep today and seen no problems. Please get some more info. Sam