[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: RH9 and WEP
- From: "Joe Polk" <listuser javelinux com>
- To: shrike-list redhat com
- Subject: Re: RH9 and WEP
- Date: Thu, 1 May 2003 13:50:07 -0400
According to the man page for iwconfig, the s: is supposed to prefix the
ASCII key when you're not manually entering hex. This is odd that the s:
would be there. Perhaps they were trying to insert it beforehand. I'll try
removing it to see what happens. Thanks!
<<JAV>>
---------- Original Message -----------
From: Keith Winston <kwinston twmi rr com>
To: shrike-list redhat com
Sent: Thu, 01 May 2003 12:37:26 -0400
Subject: Re: RH9 and WEP
> Joe Polk wrote:
> > Anyone have any luck with WEP and RH8 or RH9? I've tried 64bit and 128bit
> > keys with no luck. I can put in ASCII strings in the GUI setup, and
iwconfig
> > shows them converted fine but they never find the WAP. Take it all out
and go
> > naked, all works fine.
>
> This is a known bug. It has been bugzilled and fixed (in one of the
> RH engineers FTP sites). Sorry, I don't have links at hand.
>
> You can fix it manually by editing:
>
> /etc/sysconfig/networking/devices/ifcfg-eth1
>
> Or whatever your wireless device is. Redhat-config-network always
> converts a hex key into a string by adding an s: to the KEY= value.
> Just remove the s: part of the key. Be warned, however, that if you
> go back into redhat-config-network and change anything, it will
> mangle your hex key again.
>
> Best Regards,
> Keith
> --
> LPIC-2, MCSE, N+
> Droplets of yes and no in an ocean of maybe
> Got spam? Get spastic http://spastic.sourceforge.net
>
> --
> Shrike-list mailing list
> Shrike-list redhat com
> https://listman.redhat.com/mailman/listinfo/shrike-list
------- End of Original Message -------
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]