Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 1 Oct 2005 11:02:24 +0800 (CST)
From:      Tai-hwa Liang <avatar@mmlab.cse.yzu.edu.tw>
To:        Eric Schuele <e.schuele@computer.org>
Cc:        mobile@freebsd.org, current@freebsd.org
Subject:   Re: wpa_supplicant and WEP....
Message-ID:  <05100110534811.3012@www.mmlab.cse.yzu.edu.tw>
In-Reply-To: <433DEF54.7070201@computer.org>
References:  <433D5215.6010101@computer.org> <20050930184537.GA3665@teardrop.org> <433DA1CF.7020502@computer.org> <20050930210541.GA11841@odin.ac.hmc.edu> <433DAE00.4090602@computer.org> <20050930222442.GA20004@odin.ac.hmc.edu> <433DEF54.7070201@computer.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 30 Sep 2005, Eric Schuele wrote:
>> Brooks Davis wrote:
>> How are you entering
>> your hex keys?  The examples are a bit unclear, but digging around in
>> the code it looks like unquoted strings are assumed to be hex strings.
>> They should not be prefixed by 0x. 
>
> I'll try them in the above format (I was prefixing with 0x).  I'm not in the 
> office but will try my home AP.... BRB....
>
> Whoa!!!  That's IT!!!
> Am I the only person who couldn't figure that out???
> You must use all 4 hex keys and specify which is the default.

   That's weird.  My working wpa_supplicant.conf doesn't have "wep_tx_keyidx"
and has only one wep_key set:

 	network={
 		ssid="GoodNeighbour"
 		scan_ssid=1
 		key_mgmt=NONE
 		wep_key0="11111"
 	}

   FWIW, "11111" is the first ASCII WEP key set in my test AP(Buffalo
AirStation G54).  The rest(key 2 ~ 4) were simply empty strings in my AP's
configuration.

-- 
Cheers,

Tai-hwa Liang



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?05100110534811.3012>