Summary: | knetworkmanager doesn't tell NM about known non-broadcast ESSID networks at first startup | ||
---|---|---|---|
Product: | Network Management | Reporter: | Stefan Becker <chemobejk> |
Component: | Wireless | Assignee: | Will Stephenson <wstephenson> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | alberto.quattrinili, kontakt, lamarque |
Priority: | NOR | ||
Version: | 0.7 | ||
Target Milestone: | --- | ||
Platform: | RedHat Enterprise Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Stefan Becker
2006-09-11 11:50:07 UTC
Probably a NetworkManager problem, as indicated by the need to restart NetworkManager. What happens if you use nm-applet? Sorry, don't use GNOME :-) I wanted to file a new Bug report while this report got listed in the check for duplicates. The bug is: No GUI way to fall back to Knetworkmanager interface management mode after using manual configuration GUI for the interface. No notification about the cause of lack of management. Now i see this is explained by the #3 comment - since NetworkManager ignores all interfaces listed in /etc/network/interfaces, and that's what the knetworkmanager's manual configuration updates. To fix the issue one needs to remove the corresponding entries trom the file, just as directed in http://ubuntuforums.org/showthread.php?t=528421 , where I found out that I wasn't the only confused user. More specifically, manual configuration is not in the knetworkmanager component but it is a configuration panel from KDE that can be shown by issuing "kcmshell kcm_knetworkconfmodule". Nevertheless IMHO either knetworkmanager should not rely on NetworkManager or the "feature" of ignoring manualy configured interfaces that NM introduced should be marked as a regression bug. Let me know if repairing the interfaces file is not a remedy for this bug so I can submit a new bug report. I am sorry as my comment #3 is a mistakenly submitted comment for a different issue http://bugs.kde.org/show_bug.cgi?id=133809. Please anybody remove it if you are authorized. #3 - if you still have problems with current versions, try http://vidner.net/martin/software/cnetworkmanager/ to try to create a connection. See http://userbase.kde.org/NetworkManagement for troubleshooting tips. I have debian unstable as os with kneworkmanager at revision svn1043853. Network manager does not seem to be able to discover hidden network either with wpa or wep. Instead, if we add that network before of disabling ssid broadcast, the connection is added and I can connect to it. Then if I disable ssid broadcast it is able to reconnect to that connection. Is this still happening? Can't tell. KNetworkManager has been non-functional since the beginning of KDE4 on Fedora, so I'm not using it any more. it still happens for me. I have the version 1:0.9+git20110318.941cde9-1 on debian unstable (linux kernel 2.6.38-1). *** This bug has been marked as a duplicate of bug 209464 *** |