Bug 271561

Summary:	KNM always auto-creates wired connection, doesn't use custom config
Product:	knetworkmanager	Reporter:	Jeffrey <eljefedelito>
Component:	general	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	lamarque
Priority:	NOR
Version:	0.7 (KDE4)
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed In:

Description Jeffrey 2011-04-23 16:33:36 UTC

Version:           0.7 (KDE4) (using KDE 4.4.5) 
OS:                Linux

I created a single custom-configured wired connection that I want my computer to use at bootup, regardless of logging in to KDE (for remote network access reasons).  However, KNetworkManager always has its own auto-configured setup with a DCHP address and nameservers which I don't want (even tho the DHCP server hands out this info).

I want my custom-defined config please, and I want this to override any auto-config that may happen.  Can we have a checkbox to 'Use this profile by default' ?

Reproducible: Didn't try

Steps to Reproduce:
Boot computer, KNM shows auto-configured connection

Actual Results:  
I get an address and nameservers which I don't want

Expected Results:  
My custom-configured profile should be used; if I have multiple there should be an option to use one by default.

Thanks for KDE!

Comment 1 Lamarque V. Souza 2011-04-23 20:22:28 UTC

It is NetworkManager that creates that connection as a system connection, which has priority over user connections (the default in Plasma NM). Last week I commited a patch to allow users to edit system connections so you now you can edit that connection to suit your preferences.

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