Static network settings while in livecd do not take effect without complete restart of network setting tool and re-assertion of the device checkbox

[Nick Moffitt]

While testing the 7.10 beta desktop CD on a variety of i386 and amd64 systems, we detected a problem in the behavior of the manual network configuration tool.

If in a liveCD session, one selects System->Administration->Network or NetworkManagerIcon->ManualConfiguration (they appear equivalent) and sets up a network interface as having a static IP, the interface does not activate until one closes the network tool, restarts it, unchecks the network device's checkbox and then re-checks it again. From that point on the network interface behaves normally.

[Pharao (timo-hopelesscom)]

I can reproduce this problem with 7.10 installed on my notebook. eth0 (in my case) just doesn't come up. a simple
$ sudo ifup eth0
is enough to make it work with a static ip.

[Sebastien Bacher (seb128)]

I've sent the bug upstream on http://bugzilla.gnome.org/show_bug.cgi?id=485683. The issue is somewhat due to network-manager it doesn't happen when it's not running

[Sebastien Bacher (seb128)]

upstream comment

"gnome-system-tools just modifies the interface configuration file(s) and runs
ifup immediately on it in this case. I faced myself this problem a few times
some time ago when testing gnome-system-tools/NetworkManager cooperation code,
I found out I could reproduce it through command line too, and that everything
worked as expected if NM wasn't active.

My conclusion was that NM is not releasing properly the interface, so I'm
moving this bug there."

reassigning the bug

[vladf (vlad-chel)]

Same problem. After setting static IP from Network Manager I have only IPv6 address for eth0 interface.

eth0 Link encap:Ethernet HWaddr 00:16:D4:D8:69:1E
          inet6 addr: fe80::216:d4ff:fed8:691e/64 Диапазон:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:448 (448.0 b) TX bytes:492 (492.0 b)
          Interrupt:18

but if make "sudo ifup eth0" entered in the Network Manager IPv4 address will assigned:

eth0 Link encap:Ethernet HWaddr 00:16:D4:D8:69:1E
          inet addr:212.57.158.254 Bcast:212.57.158.255 Mask:255.255.255.240
          inet6 addr: fe80::216:d4ff:fed8:691e/64 Диапазон:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:28 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2006 (1.9 KB) TX bytes:2343 (2.2 KB)
          Interrupt:18

[Stubbspks (mamiehling)]

Same problem, but mine only seems to occur after trying to switch from wireless to wired connection or vice versa.

It also seems to happen if I switch off my wireless switch on my Dell D620

[Roman Polach (rpolach)]

In installed Hardy (final) the problem is gone for me.

[Serhey Kusyumoff (Сергій Кусюмов) (sergemine)]

I have also installed Hardy. And the problem seems to be gone for the first couple of days. But it is the same really. Same thing! I use gksu /etc/init.d/networking restart to reastart the interfaces. Hate to do it with this amazing level of automation and comfort in network settings management in Ubuntu!

[Alexander Sack (asac)]

NM 0.7 does supports static IP setups properly now in 0.7. I think this bug is fixed.

[Roman Polach (rpolach)]

I think this bug is not about static IP (i.e. not dhcp) in network manager
but about static(manual, non-roaming) network configuration, this means -without- network manager.

"Non-roaming" configuration of networking still needs /etc/init.d/networking restart
for me in Intrepid beta liveCD.
So if I am not wrong please remove "fix released" flag.