From owner-freebsd-net@FreeBSD.ORG Tue Mar 23 05:55:13 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E3B916A4CE; Tue, 23 Mar 2004 05:55:13 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 109B143D3F; Tue, 23 Mar 2004 05:55:13 -0800 (PST) (envelope-from sam@errno.com) Received: from [192.168.254.21] (61-229-32-146.HINET-IP.hinet.net [61.229.32.146]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id i2NDt95D056717 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 23 Mar 2004 05:55:11 -0800 (PST) (envelope-from sam@errno.com) In-Reply-To: <20040321013533.GA37342@panzer.kdm.org> References: <20040321013533.GA37342@panzer.kdm.org> Mime-Version: 1.0 (Apple Message framework v609) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Sam Leffler Date: Tue, 23 Mar 2004 21:55:05 +0800 To: "Kenneth D. Merry" X-Mailer: Apple Mail (2.609) cc: freebsd-net@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: WEP problems with ndis and ath drivers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2004 13:55:13 -0000 On Mar 21, 2004, at 9:35 AM, Kenneth D. Merry wrote: > > I have a Dell Inspiron 8500 laptop with an onboard TrueMobile 1300 > (Broadcom, b/g chipset) and a Netgear WAG511 cardbus card (Atheros, > a/b/g > chipset). > > I have a Netgear FWAG114 firewall/access point. (Atheros based, does > a, b > and g.) > > I'm running FreeBSD-current from Friday, March 19th. Both cards talk > to > the access point under FreeBSD when I'm not running WEP, and neither > card > works with WEP enabled. (i.e., neither card will associate with the > base > station with WEP enabled.) > > I have tried putting the key in as both hex digits and as the > passphrase I > used on the router to generate the hex key. (The router claims it's a > 128 > bit key, but it only generates 26 hex digits, so it's really a 104 bit > key > I suppose.) > > Both cards work under Windows with WEP, with either the hex key or the > passphrase entered. > > I have attached ifconfig and wicontrol output from both cards, and > dmesg > output from the laptop. > > To enable the adapter, I've been doing things like this: > > ifconfig {ath0|ndis0} ssid [my ssid] wepmode on wepkey `cat wepkey` > > (where wepkey is a file with the 26 digit hex key, starting with 0x) > > For what it's worth, I've tried setting the authmode to shared > (instead of > "open"), but all I get is the following: > > ifconfig ath0 authmode shared > ifconfig: SIOCS80211: Invalid argument > > The ath driver spits out the following diagnostics when I try to > associate > with either the a or g part of the base station with WEP on: > > > ath0: authentication failed (reason 13) for 00:09:5b:66:0d:f9 > ath0: authentication failed (reason 13) for 00:09:5b:66:0d:f9 > ath0: authentication failed (reason 13) for 00:09:5b:66:0d:f9 > ath0: authentication failed (reason 13) for 00:09:5b:66:0d:f9 > ath0: authentication failed (reason 13) for 00:09:5b:66:2c:5c > ath0: authentication failed (reason 13) for 00:09:5b:66:2c:5c > ath0: authentication failed (reason 13) for 00:09:5b:66:2c:5c > ath0: authentication failed (reason 13) for 00:09:5b:66:2c:5c > > (The first mac address is the a base station, the second is the g base > station.) > > The ndis driver (I'm using the Dell/Broadcom Windows drivers for the > onboard chip) doesn't give any error messages, but doesn't associate > either. > > If anyone has any clues on how to get this to work, I'd love to hear > them. > (Or if you have a similar setup and have managed to get it to work with > WEP, that would be > use sg.ath_ndis.out>__ It appears your AP requires shared-key authentication to associate when WEP is enabled. The current code in the tree does not support shared-key authentication (it's actually a bad idea security-wise). I have tested shared-key support in a p4 branch but haven't committed it yet. If you want it you can find it in my sam_sockets branch. Sam