Bug 238803

Summary:	knetworkmanager creates wifi connection profile in infrastructure mode despite successfully detecting ad-hoc mode
Product:	[Unmaintained] knetworkmanager	Reporter:	Tamás Németh <nt1277>
Component:	general	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	dantti12, lamarque
Priority:	NOR
Version First Reported In:	0.9
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Tamás Németh 2010-05-25 17:33:55 UTC

Version:           0.9 (using KDE 4.4.3) 
OS:                Linux

I created an ad-hoc wifi network with a Nokia 5800 XpressMusic phone, and wanted to join it. Kneworkmanager detected the network and successfully identified it as ad-hoc, but upon creating a profile for joining this network, it wanted to create an infrastructure mode network with the same SSID name. I had to change the mode manually. Can you automate this step?

Reproducible: Didn't try

Steps to Reproduce:
Create an ad-hoc wifi network, the start joining it by knetworkmanager.

Actual Results:  
The working mode of the created network is infrastructure.

Expected Results:  
Maybe it shoud be ad-hoc by default?

Comment 1 Daniel Nicoletti 2010-11-22 00:03:19 UTC

I can reproduce this too using Kubuntu 10.10 and the plasmoid NM.
The problem is when creating a new connection it does not choose adhoc, if you manually go and change it, then it works.
And btw IMO it should display a different Icon for AdHoc connections.

Comment 2 Lamarque V. Souza 2011-03-28 19:22:21 UTC


*** This bug has been marked as a duplicate of bug 212941 ***