On Wednesday 26 April 2006 20:00, Charles Curley wrote: >On Wed, Apr 26, 2006 at 06:01:00PM -0500, Paul Johnson wrote: >> I asked about wireless support in this list a couple of days ago and >> people pointed me at NetworkManager. It was not running on my >> system, perhaps because my system was installed with FC3 and then >> upgraded to FC4 and FC5, so new services were not activated as they >> would be in a fresh install. >> >> My experience is mixed. >> >> For the wired and non-encrypted wireless, it seems to be fine. >> HOwever, for the networks that require a WEP key, I can't log in >> with it. When I try with NM, it asks me for a WEP passphrase and it >> asks if I am in an "open network" or "shared network". I don't >> know what those mean, but I've tried all combinations and it does >> not log in. >> >> On the other hand, with the key saved in >> /etc/sysconfig/network-scripts, the home network does come up, >> either from the command line: >> >> /sbin/ifup home >> >> or inside system-config-network. >> >> Can NetworkManager be made to read the WEP key as it is already set >> by system-config-network? > >This sounds suspiciouly like my experience until now. What I just >discovered is that NM does not like or play with 64 bit WEP keys. You >must use 128 bit WEP keys. You might check your AP for the size of the >keys. Mine are all 128 bit, it simply ignores them. -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
