Hi --
Can somene tell me what goes on "behind the scenes" of redhat-config-network-gui? Especially with regard to creating a new wireless connection with this tool.
The reason I ask is, with Red Hat 9 on a Dell C640 and a Dell TrueMobile 1150 ( Lucent card, the orinoco driver works ), when I create a new wireless connection using redhat-config-network-gui, it doesn't work. Activating the card doesn't work, and it never gets an IP address and never contacts the nearest WAP.
However, if I then do:
iwconfig eth1 key {OUR WEP KEY},
followed by /sbin/service network restart,
it works. However, after the next reboot, it doesn't work again, and iwconfig shows no wep key.
Can someone tell me either a) how to fix this so it works with redhat-config-network-gui or b) what r-c-n-g actually does, so I can fix it myself?
Thanks,
Aaron Bennett
On Wed, 6 Aug 2003, Aaron Bennett wrote:
Can somene tell me what goes on "behind the scenes" of redhat-config-network-gui? Especially with regard to creating a new wireless connection with this tool.
You really need to poke around in /etc/sysconfig/network-scripts to understand what's going on.
Activating the card doesn't work, and it never gets an IP address and never contacts the nearest WAP.
However, if I then do:
iwconfig eth1 key {OUR WEP KEY},
followed by /sbin/service network restart,
it works. However, after the next reboot, it doesn't work again, and iwconfig shows no wep key.
have you got a KEY="YOUR WEP KEY" line in /etc/sysconfig/networking/ifcfg-eth1 ?
Thanks, Aaron Bennett
Best Regards, Alex.
rhllist@assursys.co.uk 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?
Aaron Bennett said:
rhllist@assursys.co.uk 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
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@assursys.co.uk 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?
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@assursys.co.uk 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?
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@assursys.co.uk 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?
Am Mit, 2003-08-06 um 18.40 schrieb Aaron Bennett:
The reason I ask is, with Red Hat 9 on a Dell C640 and a Dell TrueMobile 1150 ( Lucent card, the orinoco driver works ), when I create a new wireless connection using redhat-config-network-gui, it doesn't work. Activating the card doesn't work, and it never gets an IP address and never contacts the nearest WAP.
Just as an info: There is a new version of redhat-config-network on rawhide which should solve a but with (at least some) wireless cards.
PB
-
Aaron Bennett -
Harald Hoyer -
Peter Boy -
rhllist＠assursys.co.uk -
William Hooper