Network Manager fails to apply static IP address

I have not seen any recent activity with this package. Is this planned to be fixed for final release?

Before I start complaining: thnaks guys for the 9.04 Kubuntu release! I was looking forward to this release since the release of 8.10! ;-)

Anyhow, I unfortunateley I have to confirm this bug. Neither does the nm plasma widget in 9.04 Kubuntu accept static ip adresses, nor is the scaling of the widget fortunate. In my case, not even closing and reopening of the widget does give a correct scaling of the plasmoid.
If I connect to the static IP wired connection the widget does seem to do exactly nothing. It works with DHCP though. With the static IP connection set, the only reaction of the widget AT ALL is to state "not plugged in" if cable is removed completeley, which changes to "disconnected" upon plug in of the cable.

Please guys, I really love Kubuntu since 7.04, but since then never ever did the standard network applet (Knetworkmanager and now the nm widget) work completely (meaning e.g. having the same functionality as the network stack in WinXP). I have about 2-5 university friends here which love to test Kubuntu, but with these kind of serious and basic issues I just cannot advise them to try Kubuntu, which is really unfortunate, because it is not mine but YOUR creation not getting appreciated!

Elsevier

Confirming with an up2date Jaunty:
Version: 0.0+svn930811-0ubuntu2

i confirm the same bug. If you set a static ip address, close it & open it again in the subnet mask there is only 0.

It is possible to configure a static IP (I've managed it), but it's rather confusing. The subnet mask must be entered in the less common 'prefix' format, so 255.255.255.0 becomes 24 (meaning the first 24 bits of the 32 bit number), and 255.255.0.0 would be 16. I've also seen bugs with the icon not updating properly, but since I'm now running a PPA version of KDE, I can't check against the distro version. Maybe I'll hop on to Karmic to test it.

I also think that the interface for the settings could use some work, but that's a separate matter.

I confirm that I can set an static IP address in my wireless interface. I use CIDR notation, using 24 as prefix, is ALWAYS use dhcp to get ip address and silenty ignores my static IP profile. Using Kubuntu 9.04:
plasma-widget-network-manager 0.0+svn966653-0ubuntu0.1
network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2

Oops, sorry I would say CAN'T ins last comment, I can't get a static IP to work in plasma-widget-network-manager, always uses DHCP an ignores my static IP setting

Well, after the update to Karmic (9.10), the network-manager-plasmoid seems to work with static IPs now??!!!!

At least, I can get a wired connection with static IPs to work and it also remains working after several reboots in my case.

Well, I do not want to get overexcited about this, but could it be that the standard network manager in Kubuntu FINALLY works with static IPs? It didn't work since 2 years now!

That would be indeed a improvement!

Huge thanks to the guys who made it suck considerably less!!!

elsevier

I can confirm that this is fixed in Karmic. Thanks for the hard work.

I have Kubuntu 9.10 with all latest launchpad packages and despite I set static IP connection for my eth0 after booting my system gets connected by auto eth0 connection (DHCP) instead of my static connection. I have to manually reconnect to my static connection (it is set to connect automatically)
My software versions:
Network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
plasma-widget-networkmanagement 0.9~svn1029786+ag1-0ubuntu1
kde 4.3.4

I have Kubuntu 9.10 with all latest launchpad packages and despite I set static IP connection for my eth0 after booting my system gets connected by auto eth0 connection (DHCP) instead of my static connection. I have to manually reconnect to my static connection (it is set to connect automatically)

Therefore I changed bug status to Incomplete.
My software versions:
Network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
plasma-widget-networkmanagement 0.9~svn1029786+ag1-0ubuntu1
kde 4.3.4

Hi Bednar

Thanks, but that's actually a separate bug, or perhaps not a bug at all.

1) Have you set the DHCP connection *not* to automatically connect? If they're both set to auto connect, the computer might prefer the DHCP one.
2) If that's not it, try asking a support question: https://answers.launchpad.net/ubuntu/+source/plasma-widget-network-manager
3) If you can't get an answer, or you're sure that it's a bug, file a new bug report: https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+filebug

Dnia środa, 9 grudnia 2009 o 21:36:16 napisałeś:
> Hi Bednar
>
> Thanks, but that's actually a separate bug, or perhaps not a bug at all.
>
> 1) Have you set the DHCP connection *not* to automatically connect? If
> they're both set to auto connect, the computer might prefer the DHCP one.
> 2) If that's not it, try asking a support question:
> https://answers.launchpad.net/ubuntu/+source/plasma-widget-network-manager
> 3) If you can't get an answer, or you're sure that it's a bug, file a new
> bug report:
> https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+f
> ilebug
>
> ** Changed in: plasma-widget-network-manager (Ubuntu)
> Status: Incomplete => Fix Released

Hi,
thanks, I've just find a solution by editing /etc/network/interfaces by adding
following lines:

auto eth0
iface eth0 inet static

address 192.168.0.1
netmask 255.255.255.0
broadcast 192.168.0.254 (optional because not all networks use it)
gateway 192.168.0.10

and editing /etc/resolv.conf

This works! But your suggestion does not work. In my case I cannot disable
"Automatic connection" for eth0 auto in plasma-network-maganager because
automatic connection are not editable nor listed in wired (or any else)
connections.

I'm glad the solution I've found works, but I'm thinking that the same
functionality should be available in GUI for any user instead of manually
editing config files. It is not easy to find and may be to difficult for typical
user.

best regards

Bednar

You're right, that's a workaround rather than a solution. If you can still reproduce the problem, and you're happy to spend some time helping to debug it, you could file a new bug report for it.

I have the same issue in 9.10 as well.