Red Hat Bugzilla – Bug 138044
Entering hex WEP key doesn't work with my setup, and when it does, it doesn't get remembered
Last modified: 2007-11-30 17:10:53 EST
Description of problem:
NetworkManager doesn't ask a non-root user for a WEP key, it just shows an error
message that "this network is not active" or some-such, and doesn't go any further. Also,
for root, if it does ask for a WEP key, it will ask for it again next time (this is not remembered
like it should).
Version-Release number of selected component (if applicable):
every time on my laptop.
Steps to Reproduce:
1. make network service not start at boot
2. make NetworkManager service start at boot
4. log in as root user into gdm
5. start NetworkManagerInfo
6. click on the menu item in NetworkManagerInfo's applet for the SID I want to associate to
7. get prompted for the hex WEP key, even though I've entered it previously
9. log in as non-root user
10. start NetworkManagerInfo
11. click on the menu item in NetworkManagerInfo's applet for the SID I want to associate to
12. am presented with an error message saying "this network is not in range, so another
network will be used if available"
network doesn't work
network should work
I see this in /var/log/messages when I click the menu of the ESSID I want to use:
Forcing device '/org/freedesktop/NetworkManager/Devices/eth1' and network 'XXXXX'
nmwa_dbus_call_nm_method(): org.freedesktop.DBus.Error.NoReply raised:
Message did not receive a reply
Do newer versions of NetworkManager & NetworkManager-gnome seem to
work better for this problem?
Yes, actually. =:) Yay!! =:) I'm running these:
And the card asks me for the key, and it remembers it across reboots.
Ok, sounds great. Closing this one out then.