NdisWrapper nearly working - was madwifi ath_pci config problems on Sony Vaio

Rick Stevens rstevens at vitalstream.com
Fri Nov 18 21:26:50 UTC 2005


On Fri, 2005-11-18 at 10:10 +0000, Gary Stainburn wrote:
> On Thursday 17 November 2005 6:58 pm, Rick Stevens wrote:
> > 128-bit is sort of a misnomer.  The key itself is 104 bits (or 13
> > ASCII characters), to which a 24-bit (3 byte) "IV" (initialization
> > vector) is automatically added.  The whole thing is 128 bits, but you
> > only get to tweak 104 of them.  In the same manner, 64-bit WEP uses a
> > 40-bit (5 ASCII character) WEP key.
> >
> 
> Hi Rick
> 
> This makes some sense, but here's some discrepency here.  Based on what 
> you say I'd expect the AP to specify 64-bit/128 bit or 40-bit/104-bit.  
> 
> However, to confuse things, it specifies eiher 40-bit or 128-bit

Now THAT's brain-dead.  The recognized WEP encryption mechanisms are
64-, 128- and 256-bit, and use 40 bit keys (5 ASCII or 10 hex chars),
104 bit keys (13 ASCII or 26 hex chars) or 232 bit keys (29 ASCII or 58
hex chars).  Note that each one uses a 24-bit initialization vector.

> I've tried choosing 40-bit and setting a 40-bit key (as hex and as 
> ASCII) but it still doesn't work.

That's 5 ASCII characters or 10 hex characters, right?  As an example,
the ASCII key "s:abcde" is the same as the hex key "6162636465".  I just
want to make sure that you grok that.

----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-          When all else fails, try reading the instructions.        -
----------------------------------------------------------------------




More information about the users mailing list