Summary: | KNetworkManager doesn't remember my WLAN on startup | ||
---|---|---|---|
Product: | knetworkmanager | Reporter: | Henry <hklemme> |
Component: | general | Assignee: | Will Stephenson <wstephenson> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 0.1 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Henry
2006-12-23 13:28:49 UTC
Also having this problem on Ubuntu Dapper, KDE 3.5.2, knetworkmanager 0.1 prerelease (from Ubuntu package) Will test this setup myself. Would it be helpful if I posted a log file showing this activity? If so, please let me know what file knetworkmanager or networkmanager logs to, and I will post a gzipped copy. Thanks! Made a new discover tonight: It seems the [mis]behavior of my wireless LAN on startup is in some way connected to the physical WLAN button on my HP nc6230 notebook. While the LED doesn't toggle on or off with the wireless adapter, pressing the button repeatedly allows/disallows knetworkmanager to connect to my WLAN. It seems that knetworkmanager continues trying to connect to the WLAN when the card is "switched off" by the WLAN button. My network continues to show in the list (along with several others) regardless of the "state" of the adapter, so I suspect my issue is separate from the original bug posted here. My security configuration is the same, using SuSE 10.2 and KDE 3.5.6. I must manually connect to my wireless network as well since KNetworkManager connects automatically to my neighbour's wlan, that is unencrypted. I have the wireless passwd in kwallet and I've indicated to Yast to connect only to my AP's MAC, but it is ignored. Nevertheless, the kwallet's input password popup comes up from time to time. Wouldn't it be a method to make KNetworkManager remember the last wlan it was connected to?. I hope it would make kwallet's popup appear everytime I log in. David: Correct, NetworkManager did not reliably detect if the hardware rfkill switch was on or off until quite recently. Also the scan list in NM is maintained separately to that returned by iwlist (iface) scan. This behaviour is part of NetworkManager, not knetworkmanager so we can't do anything about it. I suggest you try a more recent version of NetworkManager. |