Red Hat Bugzilla – Bug 88810
KEY set incorrectly for wireless cards using multiple encryption keys
Last modified: 2007-04-18 12:53:02 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
Description of problem:
When adding a wireless card configuration, I used redhat-config-network /
wireless device configuration / wireless settings tab, and defined the settings
for my wireless network, including the encryption key (which is hex). The
redhat-config-network writes the configuration to
/etc/sysconfig/networking/devices/ifcfg-eth1 and saves the KEY value as either a
string or hex value.
The Orinoco Silver wireless card supports 4 key values and you normally specify
which key to use by following the key value with the key number in brackets.
For example, to specify key 2, use FFFF-FFFF-FF . This syntax worked
correctly in Red Hat 8. In Red Hat 9, the key above gets converted to a string
value and doesn't work (it gets stored as KEY='s:FFFF-FFFF-FF '). The
brackets seems to be throwing it off. If I enter it without the space, it still
stores it as a string. If I enter 0xFFFF-FFFF-FF , it still converts it to a
string of KEY='s:0xFFFF-FFFF-FF '.
The only way I can get it to work is to manually edit the ifcfg-eth1 file and
set the key to 'FFFF-FFFF-FF '. Then, it works normally.
The wireless tab in redhat-config-network should allow you enter a hex key and
specify which key to use without converting the key value to a string.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start redhat-config-network
2. add a new wireless pcmcia card definition, lucent orinoco silver
3. set the encryption key to a hex value using key , for example,
4. the incorrect key value will be stored in the card configuration file (it
will be converted to a string).
Actual Results: It created a string key instead of a hex encryption key value.
Expected Results: It should have stored a hex encryption key value.
redhat-config-network worked correctly in Red Hat 8.
*** This bug has been marked as a duplicate of 88566 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.