Bug 153232

Summary:	Networkmanager: cannot connect to ad-hoc networks with knetworkmanager
Product:	[openSUSE] openSUSE 11.1	Reporter:	Forgotten User ZhJd0F0L3x <forgotten_ZhJd0F0L3x>
Component:	KDE3	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Enhancement
Priority:	P4 - Low	CC:	andrew.james.barr, forgotten_mbQyAD5r4K, helmut.schaa, mteixeira, suse-beta, w.posche, wstephenson
Version:	Alpha 2
Target Milestone:	---
Hardware:	i686
OS:	Other
Whiteboard:
Found By:	Component Test	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User ZhJd0F0L3x 2006-02-23 22:38:28 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

Comment 1 Quentin Jackson 2006-04-13 22:28:12 UTC

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.

Comment 2 Timo Hoenig 2006-04-18 00:32:05 UTC

*** Bug 166217 has been marked as a duplicate of this bug. ***

Comment 3 Mauricio Teixeira 2006-04-22 12:33:24 UTC

Issue remains on SUSE 10.1 RC1.

~> rpm -qa Network*
NetworkManager-kde-0.1r527269-3
NetworkManager-0.6.2-10

Comment 4 Timo Hoenig 2006-04-25 14:47:03 UTC

Possibly a candidate for LATER (update package).  Depends on how I get along with the more severe bugs.

Comment 5 Timo Hoenig 2006-05-16 09:42:23 UTC

Moving to 10.2.  I will provide update packages for 10.1 once this is implemented.

Comment 6 Jens Uhlenbrock 2006-11-07 07:48:23 UTC

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.

Comment 7 Timo Hoenig 2006-11-07 09:24:50 UTC

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.

Comment 8 Forgotten User ZhJd0F0L3x 2006-11-07 10:20:05 UTC

Jens, also doublecheck that your university wireless lan is really an ad-hoc network. I doubt it. Otherwise it would be a different bug.

Comment 9 Jens Uhlenbrock 2006-11-07 11:06:52 UTC

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%.

Comment 10 Timo Hoenig 2007-01-09 13:57:59 UTC

→ OS10.3

Comment 12 Helmut Schaa 2007-09-10 09:46:22 UTC

Moved to 11.0.

Comment 13 JP Rosevear 2008-01-23 19:31:55 UTC

Is this solved with NM 0.7?

Comment 14 Helmut Schaa 2008-03-05 16:05:38 UTC

Not fixed in KNM 0.7 yet.

Comment 16 Christian Zoz 2008-10-21 11:53:14 UTC

Moving to 11.1

Comment 17 Christian Zoz 2009-07-02 09:45:49 UTC

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.