KNetworkManager doesn't work with static IP configuration

[disabled.user]

While NetworkManager in Ubuntu Feisty Beta 1 works fine for me with static IP configuration, unfortunately KNetworkManager in Kubuntu Feisty Beta 1 does not.

Whenever I try to convince KNetworkManager that I want e.g. 192.168.0.10 as my static address, KNetworkManager pretends to apply my changes, but the IP remains at the auto-assigned private 169...-type. Directly changing network setting via kcontrol also doesn't do anything.

I have to shut down KNetworkManager, manually edit /etc/network/interfaces and use ifupdown-tools to configure my network, which works as supposed.

[Lars M Bengtsson (lars-m-bengtsson)]

Hi!

I had about the same problem with it - the IP address stayed the same despite the fact that knetworkmanager seemed to apply the settings. Eventually a reboot of the machine caused the new settings to take effect (I guess a restart of networkmanager would have been enough, though).

The DNS domain settings also seems to need some updates. If I enter a number of domains that I want to have in my search list, then the list gets prefixed with "domain" in the /etc/resolv.conf file, which is wrong - when several domains are listed the list should be prefixed with "search" if I am correctly informed.
This breaks the domain search, and also causes the "dig" utility to say "parse of /etc/resolv.conf failed".
Changing "domain" to "search" by hand in the /etc/resolv.conf file fixes all the problems, but knetworkmanager does not pick up this change when the static config is opened again.

I'm having this issue on a new installation of Kubuntu Beta 1.

Best regards,
Lars

[Lars M Bengtsson (lars-m-bengtsson)]

Hi again,
Just an additional note, to avoid confusion: I realize that I left out the small detail that I had the above problem with a wired network, not wireless.

It's not completely clear which kind of network the original reporter had problems with, so perhaps this should have been a separate bug report...

Best regards,
Lars

[disabled.user (disabled.user-deactivatedaccount)]

The bug report was intended for a wired connection. In my ambiguous mind, I tend to "synonymize" static with wired networking...

[Scott Kitterman (kitterman)]

Should be fixed in knetworkmanager 0.1-0ubuntu12. Please report back if that update doesn't solve your problem and I'll reopen the bug.

[Matthew Carpenter (matt-eisgr)]

I am still experiencing this with the latest Feisty, using Wireless/WPA and a static IP address/DNS/Routes/etc...
Static IP addressing is *not* just for Wired connections. My colleagues (who largely use Mac's) are laughing at me because I can't get NetworkManager (or indeed KNetworkManager) to stop re-enabling dhclient, even after I kill it.

While I can understand how this behavior may go unnoticed for most people, some configurations do require Wifi to use Static IP addressing/etc. This is still a bug.

Rebooting is not acceptable, what are my other options for a workaround until this gets fixed?

[OrkanSpec (orkanspec)]

Kubuntu Gutsy - Tribe 5
When I start Live CD with Gutsy and configure static IP (wired), I can only ping to hosts, but e.g. I cannot open a www site in Konqueror. The only way to solve the problem is to close KNetworkManager from the system tray. Just after closing KNetworkManager, www sites open in Konqueror.
I had the same problem (or similar) in Feisty. I had to close KNetworkManager to connect to internet.