Red Hat Bugzilla – Bug 155551
NetworkManager never returns with error on wrong password/key
Last modified: 2007-11-30 17:11:04 EST
At work I have a host of wireless networks within range. The only one I am
interested in is our own. If I enter wrong password/key in network manager it
never returns saying it was unable to connect, instead it just tries some of the
other networks. Since one of those networks is open it always connects to that
instead, which I find rather frustrating. Only way to be allowed to retype the
network password/key is to delete it with gconf, which I don't think is a very
userfriendly option. If I manually tell NetworkManager to connect to a specific
network it should give me error dialogs until I am actually connected to that
Can you post the output of /var/log/messages after starting NetworkManager and
after you've tried once to connect to your access point using "Other wireless
Never connected using 'Other Wireless Networks' before, just tried the dialog
that pops up when you choose your network of choice from the list. With Other
Wireless networks I was able to log in today. Thanks. On the other hand with the
dialog that pops up when you just choose the network from the list seems even
more broken now, with current devel packages the 'Login to network' button is
greyed out no matter what. (attaching screenshot)
Created attachment 114342 [details]
Screenshot of network login dialog (which is grey no matter what)
128-bit Hex WEP keys have 26 characters, but I counted 28 in your screenshot.
Are you sure that's the right key?
it is a bogus key, I altered it heavily (by random key pressing and deleting)
before taking the shot as I felt it would be kinda stupid to post a shot with
our actual key in it :)
Switching to any of the two other options (passphrase or ascii) it is also still
Ok, the greyed-out OK button should be fixed in CVS HEAD and will also be in an
FC4 update right after FC4 comes out.
Closing bugs in MODIFIED state from prior Fedora releases. If this bug persists
in a current Fedora release (such as Fedora Core 5 or later), please reopen and
set the version appropriately.