| Summary: | 128-bit | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Christopher Chin <cchin> |
| Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Christopher Chin
2006-04-17 19:40:14 UTC
On Mon, Apr 17, 2006 at 06:38:55PM +0000, Christopher Chin wrote: > After a recent cvsup, buildworld, and new kernel, I can no longer > effectively use 128bit wep with my wi0 driver. > > This worked beautifully with my 5.4, and I'm pretty sure this worked > well after my upgrade to 6.0 and 6.1-PRERELEASE. > > > bubble (cchin):/home/cchin# ifconfig wi0 wep wepkey 0x12345678901234567890abcdef > ifconfig: SIOCS80211: Invalid argument > bubble (cchin):/home/cchin# > From the ifconfig(8) manpage: : A WEP key will be either 5 or 13 characters (40 or 104 bits) : depending of the local network and the capabilities of the : adaptor. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer State Changed From-To: open->closed The 108-bit key is understood to be the correct behavior. On Mon, 17 Apr 2006 (21:49 +0300), Ruslan Ermilov wrote: > Date: Mon, 17 Apr 2006 21:49:04 +0300 > From: Ruslan Ermilov <ru@freebsd.org> > To: Christopher Chin <cchin@ack.Berkeley.EDU> > Cc: freebsd-gnats-submit@freebsd.org > Subject: Re: bin/95956: 128-bit > > On Mon, Apr 17, 2006 at 06:38:55PM +0000, Christopher Chin wrote: >> After a recent cvsup, buildworld, and new kernel, I can no longer >> effectively use 128bit wep with my wi0 driver. >> >> This worked beautifully with my 5.4, and I'm pretty sure this worked >> well after my upgrade to 6.0 and 6.1-PRERELEASE. >> >> >> bubble (cchin):/home/cchin# ifconfig wi0 wep wepkey 0x12345678901234567890abcdef >> ifconfig: SIOCS80211: Invalid argument >> bubble (cchin):/home/cchin# >> >> From the ifconfig(8) manpage: > > : A WEP key will be either 5 or 13 characters (40 or 104 bits) > : depending of the local network and the capabilities of the > : adaptor. Thanks, Ruslan.... however, I suppose that 5 or 13 characters refers to ASCII representations. The number of hex digits will differ. - Christopher ====================== On Mon, 17 Apr 2006 (21:49 +0300), Ruslan Ermilov wrote:
>
> On Mon, Apr 17, 2006 at 06:38:55PM +0000, Christopher Chin wrote:
>>
>> [. . .]
>>
>> bubble (cchin):/home/cchin# ifconfig wi0 wep wepkey
>> 0x12345678901234567890abcdef
>> ifconfig: SIOCS80211: Invalid argument
>> bubble (cchin):/home/cchin#
>>
> From the ifconfig(8) manpage:
>
> : A WEP key will be either 5 or 13 characters (40 or 104 bits)
> : depending of the local network and the capabilities of the
> : adaptor.
Thanks, Ruslan.... however, I suppose that 5 or 13
characters refers to ASCII representations. The number
of hex digits will differ.
- Christopher
======================
On Mon, 17 Apr 2006 (19:50 -0000), Mark Linimon wrote:
>
> Synopsis: 128-bit
>
> State-Changed-From-To: open->closed
> State-Changed-By: linimon
> State-Changed-When: Mon Apr 17 19:49:11 UTC 2006
> State-Changed-Why:
> The 108-bit key is understood to be the correct behavior.
Hmmm... turns out that a better answer would have been
for me to (re-)read the 6-0 Release Notes...
particularly section 2.2.2.2. Network Interface Support.
Apparently: "Note in particular that WEP now requires
the wlan_wep module to be loaded (or compiled) into the
kernel."
All fine and good... but I'd be surprised if others
don't trip on this as well when 6.x gets more usage.
Oh... Sorry about the lame subject line. I hit the
submit button before going back and "fixing" the Subject.
Thanks,
- Christopher
======================
|