From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 01:00:37 2004 Return-Path: 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 D99AC16A4CE for ; Wed, 17 Nov 2004 01:00:37 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3F4A43D62 for ; Wed, 17 Nov 2004 01:00:37 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAH10bQo047506; Tue, 16 Nov 2004 17:00:37 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAH10acB047505; Tue, 16 Nov 2004 17:00:36 -0800 (PST) (envelope-from sgk) Date: Tue, 16 Nov 2004 17:00:36 -0800 From: Steve Kargl To: Brooks Davis Message-ID: <20041117010036.GA47474@troutmask.apl.washington.edu> References: <20041117003518.GA47238@troutmask.apl.washington.edu> <20041117005247.GB13628@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041117005247.GB13628@odin.ac.hmc.edu> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: 128bit WEP keys and ifconfig X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Nov 2004 01:00:38 -0000 On Tue, Nov 16, 2004 at 04:52:47PM -0800, Brooks Davis wrote: > On Tue, Nov 16, 2004 at 04:35:18PM -0800, Steve Kargl wrote: > > > > Other than using a 64-bit key, is there some way to > > force FreeBSD to work? > > 128-bit WEP actually uses 104-bits of key material which corresponds to > 13 ASCII characters or a 26-digit hex key. Shorter, zero-padded keys > will work, but you appear to be using something longer. > Thanks, Brooks. Netgear's docs aren't the greatest. It wasn't clear whether the string was ascii or hex, (it was given without the 0x prefix). -- Steve