Bugzilla – Bug 153232
Networkmanager: cannot connect to ad-hoc networks with knetworkmanager
Last modified: 2009-07-02 09:45:49 UTC
I cannot connect to my newly created ad-hoc network. Netcontrol works fine. No encryption etc. involved, plain unencrypted ad-hoc network. WLAN card here is ipw2200, NM is the version from beta4 (i had no need to upgrade yet :-) root@susi:/etc/sysconfig/network> rpm -qa Network* NetworkManager-0.5.1cvs20060215-2 NetworkManager-novellvpn-0.3.2-7 NetworkManager-kde-0.1r5741-2
Just a comment (I'm not a developer) but I should expect that since you say something doesn't work that that gives you the very need to upgrade. Since Suse is now RC1 which is exactly 6 updates since your version I would suggest it's a very good idea to do this.
*** Bug 166217 has been marked as a duplicate of this bug. ***
Issue remains on SUSE 10.1 RC1. ~> rpm -qa Network* NetworkManager-kde-0.1r527269-3 NetworkManager-0.6.2-10
Possibly a candidate for LATER (update package). Depends on how I get along with the more severe bugs.
Moving to 10.2. I will provide update packages for 10.1 once this is implemented.
I think I'm seeing the same bug on my Factory installation of 10.2. If it tries to connect to the unencrypted network, knetwork-manager will stop at 28% and then fail to connect. This was already a bug in 10.1. Really should be fixed in 10.2 final, though!! Otherwise it renders Suse unusuable in my university wireless lan.
Jens, it's not a bug, it's just a missing feature. Feel free to use nm-applet until KNetworkManager is providing support for creating ad-hoc networks.
Jens, also doublecheck that your university wireless lan is really an ad-hoc network. I doubt it. Otherwise it would be a different bug.
Oh, yeah, that seems to be wrong. Actually, I didn't really know what an ad-hoc network was, but after reading up on it, it doesn't seem to fit my case. We are using an 'verwaltet' (Infrastructure network?) network at home, and it doesn't work at home neither. We are using an access list of MAC addresses in order to restrict access to the network. Since other clients are running perfectly, we probably won't change this setup. So, I guess, it is not an ad-hoc network. I will look for a correct bug report to submit to. Anyway, network manager stops connecting after 28%.
→ OS10.3
Moved to 11.0.
Is this solved with NM 0.7?
Not fixed in KNM 0.7 yet.
Moving to 11.1
KNetworkManager for KDE3 is not maintained any longer. Therefore I resolve all bugs that are still open as WONTFIX without looking at each single bug report. If this bug deals already with KDE4 and is still in progress, then please apologize the mistake and feel free to reopen it.