NdisWrapper nearly working - was madwifi ath_pci config problems on Sony Vaio
Rick Stevens
rstevens at vitalstream.com
Thu Nov 17 18:58:21 UTC 2005
On Thu, 2005-11-17 at 18:46 +0000, Gary Stainburn wrote:
> On Thursday 17 November 2005 6:30 pm, Gary Stainburn wrote:
> > I don't use dashes either, but put them in to try. It made no
> > difference. I am in the same boat as you, the link works fine
> > provided I don't use encryption.
> >
> > Has ANYONE got it working with WEP?
> >
> > > Thanks,
> > > James
>
> I think I may hav found the problem. I'm specifying a 128-bit key
> because that's what my AP's got set, but the following output shows
> this to be a problem. Anyone care to comment?
>
> [root at lcomp5 ~]# iwlist wlan0 key
> wlan0 2 key sizes : 40, 104bits <-------------------------
> 4 keys available :
> [1]: 546F-2062-6520-6F72-206E-6F74-20 (104 bits)
> [2]: off
> [3]: off
> [4]: off
> Current Transmit Key: [1]
> Security mode:open
> Authentication capabilities :
> WPA2
> CIPHER TKIP
> CIPHER CCMP
> Current key_mgmt:0x0
> Current cipher_pairwise:0x0
> Current cipher_group:0x0
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.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com -
- VitalStream, Inc. http://www.vitalstream.com -
- -
- "Microsoft is a cross between The Borg and the Ferengi. -
- Unfortunately they use Borg to do their marketing and Ferengi to -
- do their programming." -- Simon Slavin -
----------------------------------------------------------------------
More information about the fedora-list
mailing list