That did it. I'm sorry to have wasted your time... the dialog clearly
instructed me to do that too, and I missed it. Thanks for responding.
It's this sort of thing that makes Red Hat the unique company that it
is. You rock.
Again, thank you.
- Aaron
Harald Hoyer wrote:
if you want a hexadecimal key, then prefix it with "0x" in the dialog
Am Do, 2003-08-07 um 15.41 schrieb Aaron Bennett:
Harald --
Thanks again. I tried again using redhat-config-network-1.2.15-1,
redhat-config-network-tui-1.2.15-1, and rhpl-0.93.4-1, and it is still
broken.
Here's a reproducer:
1. kickstart a box fresh
2. install latest versions of r-c-n, r-c-n-tui, and rhpl
3. click Hat menu / System Settings / Network
4. click "new"
5. select wireless connection
6. select the first wireless card from the "select wireless device"
menu. (in my case, it's "Lucent Orinoco and Prism II-based PCMCIA
wireless (eth1)")
7. enter the WEP key in the Key section of next screen
8. click next, then apply
9. /etc/sysconfig/networking/devices/ifcfg-eth1:
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
USERCTL=no
PEERDNS=yes
GATEWAY=
ONBOOT=yes
TYPE=Wireless
DHCP_HOSTNAME=
IPADDR=
DEVICE=eth1
HWADDR=00:02:2d:6c:a8:5d
BOOTPROTO=dhcp
DOMAIN=
NETMASK=
ESSID=
CHANNEL=1
MODE=Managed
KEY=s:{my web key}
RATE=11Mb/s
[root@studentc640 root]# rpm -qa redhat-config-network
redhat-config-network-1.2.15-1
[root@studentc640 root]# rpm -qa redhat-config-network-tui
redhat-config-network-tui-1.2.15-1
[root@studentc640 root]# rpm -qa rhpl
rhpl-0.93.4-1
Should I open a new bugzilla report, or attach this to existing bug @
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88566 ?
Harald Hoyer wrote:
better try the version from:
ftp://people.redhat.com/harald/redhat-config-network/1.2.15-RH9
Am Do, 2003-08-07 um 14.35 schrieb Aaron Bennett:
Harald --
That's good news. I tried using redhat-config-network-1.3.1-1 from
rawhide, and the bug is still there. It's somewhat different from the
bugzilla report posted above, however.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88566 is regarding
improperly importing an existing wep key. What I've found here is that
when you create a new wireless connection, it inserts "s:" into the new
key that I've just entered via the GUI.
Am I using the corrected version? I didn't mess with the initscripts.
However, I did update redhat-config-network-tui and rhpl.
(redhat-config-network-tui=1.3.1-1, rhpl=0.108-2).
Thanks,
Aaron
Harald Hoyer wrote:
the bugfix erratum is in the rhn queue. i didn't want to release
another buggy version, so it took me 15 versions to stabilize it ...
1.2.15 will soon hit your up2date.
if you use the rawhide version you have to update your initscripts as
well..
Aaron Bennett wrote:
excellent. I see there's an update in rawhide as well.
Just wondering... why isn't that update released as part of Red Hat 9
updates, available on rhn and @ your friendly neighborhood apt
repository? How does Red Hat decide what makes something worth being
release as part of the updates?
William Hooper wrote:
Aaron Bennett said:
rhllist@xxxxxxxxxxxxxx wrote:
have you got a KEY="YOUR WEP KEY" line in
/etc/sysconfig/networking/ifcfg-eth1 ?
ahhhh. In /etc/sysconfig/network/ifcfg-eth1, what I have is:
KEY="s:{MY WEP KEY}"
I changed it, taking out the s:, and it now works.
So, what is this "s:" in the KEY entry? Where did it come from?
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88566
--
Aaron Bennett
UNIX Administrator
Franklin W. Olin College of Engineering
