| Summary: | KNetworkManager connects to untrusted network instead of trusted | ||
|---|---|---|---|
| Product: | [Unmaintained] knetworkmanager | Reporter: | MartinG <gronslet> |
| Component: | general | Assignee: | Will Stephenson <wstephenson> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Still around in knetworkmanager-0.1-0.5.svn20061113.fc6 Is there any other place I am supposed to report this...? I am experiencing this same problem. I checked the knetworkmanagerrc file in ~/.kde/share/config/ and changed the "Trusted=true" line to "Trusted=false" for my neighbor's access point, but it still defaults to this when logging into KDE. Moreover, my WPA-secured network (with SSID not broadcast) is not shown in the context menu. The only way I can connect to my network is to re-enter all the information under "Connect to Other Wireless Network..." Does it work if you remove the neighbour's network from ~/.kde/share/config/knetworkmanagerrc entirely? After we wrote knetworkmanager we found out that NetworkManager doesn't really respect the trusted flag, so it's of little use. The recommendation is to delete untrusted networks entirely. Thanks for following up! I'm really looking forward to getting this working as I prepare to purchase a new laptop (experimenting on my work laptop, booting from USB right now)...
I tried deleting the neighbor's network from my knetworkmanagerrc file quite some time ago, leaving my network present. It reads as follows:
[Network_{some-random-string}]
ESSID=homewlan
Encryption=WPA
HardwareAddresses=,{my-ap's-mac-address}
Timestamp=2007,3,7,20,40,17 <--- last time I manually entered info to connect
Trusted=true
WPAProtocol=TKIP
WPAVersion=WPA1
[EOF]
This _did_ work to stop automatic connection to my neighbor's network, but (as noted in bug 139164) it still won't connect to my network instead.
If I move this file to knetworkmanagerrc.old, and touch an empty knetworkmanagerrc, then try to enter my WLAN's information manually (as always) using "Connect to other wireless network..." then knetworkmanager crashes and reloads after a 120-second timeout at "Configuring Device".
Replacing my original knetworkmanagerrc file (as above) allows me to manually connect to my homewlan using "Connect to other wireless network..." but in no case will it connect automatically on bootup. It has, however, stopped connecting to the untrusted neighbor's network since I removed that from knetworkmanagerrc.
It's an upstream networkmanager 0.6 bug that it doesn't support the trusted flag correctly. We've made it easier to delete undesired connections in knm 0.7, but that's the workaround, not the root cause in 0.6. |
Version: 0.1-0.3.svn20060625.fc5 (using KDE KDE 3.5.4) Installed from: I Don't Know OS: Linux Hi and thanks for this great software! In my house I have two wireless networks: My own, with WEP encryption ("MINE"), and my neighbors without encryption ("NEIGHBOR"). In the network list ("Options" -> "Show networks...") I have moved "NEIGHBOR" to "untrusted", but each time I boot, KNetworkManager automatically connects to this network (after I have intered my password in KWallet). I would prefer it not to, and instead connect to my network (which it can do after I have entered the password in kwalletmanager).