Hi.

I have opened a long time ago a bug about plasma-widget-networkmanagement in Kubuntu:
https://bugs.launchpad.net/ubuntu/+sour ... bug/388648

I'm still affected by the same bug even in 10.10, and there seems to be no progress towards it.

Should I also report this bug to KDE bugs? The problem is that I'm not sure whatever this is a KDE bug or a Kubuntu bug...

This isn't a bug in either actually, it is a misunderstanding assuming your interface is under the control of NetworkManager. The best way to think of it is as network profiles. The default, system wide profile is to have a DHCP assigned IP address, which cannot be edited.

If you click on the Network Management applet in the tray, you should see something similar to the following: http://simplest-image-hosting.net/jpg-0 ... ktopic3464

If your network requires a static IP address, then please follow these steps:
1) Open System Settings > Network Settings > Network Connections > Wired
2) Press Add, and setup the settings appropriately.
3) After saving, your new named profile should be available from the system tray applet, selecting it will apply that profiles settings.

Thank you for your answer. Can't test it right now (@work), but what you say is interesting.

I expected the "Wired" tab to list all interfaces, including auto-configured ones. I didn't expect it to be used only for "profiles".

So, if I will add a profile with a static IP, it will be applied automatically for the chosen interface (eth0 in my case) after every restart? Also, can the profile specifically target a certain interface (eth0)?

And another question, do you think that it will be possible in the future to also list there some kind of "surrogate profiles" for the initial auto-configured profiles, with DHCP? So people will not have to look around docs and forums for almost 2 years before being able to manually configure their network connections? I mean, it would be much easier to see there an "Auto-configured eth0" when opening the "Wired" tab (instead of nothing), it would be pretty straightforward to think about Editing that and modifying the settings...

I am not aware of any plans by the developers to make changes to the "Profiles" method of working.

Note that changing the system wide default DHCP profile likely requires root permissions, and may not even be possible (as it may be hard-coded into NetworkManager, the system wide service which Network Management simply provides your user profiles to)

In terms of being active, you can tick the "Connect Automatically" option, but I do not know if that will work. You can target a specific interface, see the Ethernet > Restrict to Interface option of each profile.

Thank you, what you said solved my problem. Marking topic as Solved.