https://bugzilla.novell.com/show_bug.cgi?id=299145#c10 --- Comment #10 from Hartmut Meyer <hartmut.meyer@novell.com> 2007-08-15 03:19:40 MST --- Yesterday I saw - to my surprise - that nm-applet did succeed in connecting to this hidden/unencrypted wireless network. Same "side effect" as described in comment #7, though: --- snip ----- 5. see knetworkmanager complete the connection 6. check with "iwconfig" ... .. and be surpised that the ESSID now is "johann-eilers-weg_24z" (note the additional 'z' at the end of the ESSID) - but connection works. knetworkamanger shows the correct ESSID (without the additional 'z' that is reported by "iwconfig"). --- snap ----- However, after a reboot, nm-applet failed just as before. I then tried with the KDE install (have two parallel installations of 10.3 beta1: one with the KDE CD and one with the Gnome CD) and there, too I could see knetworkmanager successfully connect to this network. But like nm-applet it isn't stable: after "rcnetwork restart" or reboot chances are high that it will not connect. When it connects iwconfig again shows the additional 'z' at the end of the ESSID). I'm wondering if this might be related to the observation that another user made here: https://bugzilla.novell.com/show_bug.cgi?id=242137#c8 --- snip ----- 2. I discovered more details about the wrong behavior of KNetworkManager: If KNetworkManager rejects the key once, then it keeps rejecting. The user gets a new chance by terminating and restarting KNetworkManager. The “keeps rejecting until restart” gives the user the impression that he has no chance at all. This is not right. After a restart there is a good chance (at least higher than 50 percent) to succeed. --- snap ----- Note that that report was about access to encrypted networks on 10.2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.