Archived from groups: alt.internet.wireless (
More info?)
On 17 Oct 2004 07:05:02 GMT, roberson@ibd.nrc-cnrc.gc.ca (Walter
Roberson) wrote:
>In article <1pk3n09df2csbjn6nnqo5d0eu8noppq8vs@4ax.com>,
>Jeff Liebermann <jeffl@comix.santa-cruz.ca.us> wrote:
>:The usual Mac specific problem is that Apple wants you to specify the
>:type of WEP key (also known as password) with a suitable prefix. If
>:it's in Hexadecimal, you preceed it with either a "0x" or a "$"
>:depending on driver version. Try both. One should work.
>
>I don't know about OSX 10.2.8 that the OP was running, but in
>10.3 at least, the GUI will count the number of characters provided and
>make assumptions about the numeric base of the passphrase if the
>passphrase matches the typical magic lengths. Or to put it another
>way, if it is the right size to be a complete hex string, it assumes
>it is a hex string, and if it the right size to be a maximal ascii
>passphrase, then it assumes that it is an ascii passphrase.
>Saves having to put in the 0x or $ if you are working in hex.
Time for a rant on Apple Wireless. I just finished setting up an
Airport Extreme and a new iBook G4 for a customer. She was busy
answering all the questions during the iBook startup so I just used
the Windoze Airport setup utility (4.0.2) on my PC to get the Airport
Extreme running. It was a bit non-typical as there was an existing
router. I therefore had to setup the Airport as a wireless bridge and
disable the DHCP server. I had a wonderful diversion figuring out the
apparently random selection of the IP address range as it would go
through all the RFC-1918 IP blocks until it found one it liked. With
the DHCP server off, the MAC address sniffer in the setup utility
would not find the Airport unless the PC's IP address was already set
to an IP address within its range. I had to constantly change the
laptops IP address to follow the changes and was eventually able to
nail down the Airport to a static IP address in the routers IP block.
Switching to the iBook G4 10.3.1. Initial setup was using no
encryption and working quite nicely. However, when I enabled
encryption on the Airport, it didn't bother asking 64/128bit WEP (no
WPA) key length as you mentioned. I just picked something stupid (I
was in a hurry) and it worked. No complaints about key length or
padding to 5/13 characters. Everything worked just fine. We soon ran
into some PC file sharing oddities in 10.3.1 so we immediately
upgraded to 10.3.2. Fixed and working. I thought I was done. Wrong.
When I went to setup WEP on a Dell Inspiron 5150 laptop, I ran into a
problem. The WEP key wouldn't work. 30 mins later, I found that WEP
was in 64 bit WEP mode. Makes sense since the Airport didn't bother
asking if I wanted 64 or 128 bit encryption. What it did was
"automatically" decide that since my stupid WEP key was between 5 and
13 characters, I must obviously want 64 bit encryption. It may have
truncated my selection of WEP key to 5 characters. The client
software apparently does the same thing. The PC wasn't smart enough
to do that. So, I reset the ASCII WEP key to exactly 13 characters,
and everything worked normally from there as 128 bit WEP.
I don't have anything against such automatic setups and assumptions on
the part of Apple (and other manufactories). What bugs me is that
they don't bother announcing their assumptions or documenting their
behavior. I also have some nasty things to say about the creative
terminology, metaphors, and buzzwords used by Apple, their inability
to distinguish between WAN and LAN side configuration in the Airport
Extreme, and their over automation of the install. None of the
aformentioned is fatal, but it does bug me.
--
Jeff Liebermann jeffl@comix.santa-cruz.ca.us
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558