From: Benjamin Reed/Almaden/IBM <breed@al...> - 2000-10-19 21:34:27
Well, I was home sick today. That together with WAP being turned on at
work and home caused me to update the driver. I have placed a new version
of airo.c on the web site. It has more support for WEP: (It works fine
for me, but I haven't done that much testing. I would be greatly
interested in feed back. BTW, I would like to also hear from anyone who
can/can't using this with SMP...)
1) I've changed the "syntax" for setting wep keys to: keyindex key, so
that you can set all four keys. (NOTE: As most people who are of a
reasonable mind, I consider the first key to be 0, not 1 as with the WepKey
tool for windows. I also think that the integer 1 should have a bit set on
the last byte, but that is another matter...)
echo 0 11:22:33:44:55 > /proc/aironet/eth0/WepKey # set the first key to
echo 3 11:22:33:44:55:66:77:88:99:00:11:22:33 > /proc/aironet/eth0/WepKey #
set the 4th key to a "128-bit" key
2) You can also select a transmit key by writing the number followed by a
linefeed to WepKey:
echo 2 > /proc/aironet/eth0/WepKey # set the 3rd key as the transmit key
3) I've enhanced auto_wep to cycle through the transmit keys when trying
"shared" WEP. The number of keys that are tried are specified in the
auto_wep module option. To try all 4 keys auto_wep should be set to 4.
Note: I cannot cycle through the keys for "encrypt" since you are able to
associate to an AP with an invalid key with WEP set to encrypt. I have the
module "airo" opts "ssids=SuperSecret auto_wep=4"
at the end of /etc/pcmcia/config.opts.
4) I've also made it so that if you cat /proc/aironet/eth0/WepKey, it shows
you the key lengths of the set keys, and the index of the transmit key.
Before anyone asks: somehow 8 bits times 13 = 128-bits in Aironet land :).
I'm not qualified to explain it to you...
If you are using pcmcia-cs-3.1.21 (actually even some of the earlier ones
should also work), you can simply replace the wireless/airo.c in there with
http://www.cse.ucsc.edu/~breed/airo.c. Older pcmcia packages will probably
need to hack around including http://www.cse.ucsc.edu/~breed/airo.h as
As always Jim Venesky's hints were more than invaluable in figuring out how
to do this.
what about 2.4 i365 support ?
currently, AFAIK, last 2.4.0-test series have i365 PCMCIA support
explicitly non-working... i.e. only cardbus working.
I have been again not following linux-kernel for some time, does anyone
knows the answer ?