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
