Red Hat Bugzilla – Bug 147305
config cannot set parameters for wireless; WEP scrambled
Last modified: 2008-02-05 11:54:56 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
Cannot alter any setting on the Wireless Setting tab of the
Wireless Device Configuration without getting an error
message. If all the settings are set with iwconfig
prior to using system-config-network the WEP is
scrambled Even when the key is correctly set (using 0x)
(I use a 40 bit key) it gets scrambled into a 96 bit
Can get the link to work if everything is set using
iwconfig, using system-config-network to activate and
while this is happening using iwconfig to reset the
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure device using iwconfig
2. try to activate using system-config-network
3. no link - WEP is now a (random?) 96 bit string
Actual Results: No link with wireless device
Expected Results: Network link should have been established
System : Dell Inspiron 8100 laptop with Linksys WPC55AG adaptor
(PCMCIA) using madwifi-0.0.20050128-1
hmm, please check /etc/sysconfig/network-scripts/keys-<devicename>
so it doesn't seem to be recognizing the '0x' as hex and is
treating it as a string?
well, well, you did not enter the hexstring correctly.. "-" are not
part of a number :), ok, partly my fault.
Just enter "0xF6E2B565C0" and all should be fine.
Oops! that was stupid on my part - the WEP works now.
However, the first problem remains - any attempt to
alter the wireless settings results in the message
(the example is for set mode Auto, so one can define
the channel and rate)
Error for wireless request "Set Mode" (8B06) :
SET failed on device ath0 ; Invalid argument.
Using iwconfig: "/sbin/iwconfig ath0 Auto"
gives the same message so this is a problem
with madwifi?? - or is Auto not a valid setting
for certain cards?
exactly... auto does not seem to be a valid setting for some cards :-/
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Fedora Core 3 is not maintained anymore.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release please reopen this bug and assign it to the corresponding