[Bug 1041356] Re: ifupdown not working when multiple interfaces

Teodori Serge 1041356 at bugs.launchpad.net
Fri Sep 7 03:22:17 UTC 2012

Unfortunatly no, I replaced in '/etc/init/networking.conf' 'ifup -a'
with 'ifconfig eth0 up', etc. and I appended an 'dhclient
eth0'. This solution works, but I had also to change other init scripts,
to avoid blocking when waiting for some event. The problem can be very
easily reproduced (I reproduced it in a virtual machine). Just create a
few interfaces eth0, eth1, eth2, etc. then run 'ifup eth0' through 'ifup
ethX', check '/run/network' and THERE you see some 'if*' files are
missing. Now try to shutdown an interface 'ifdown eth1' and if some
files were missing you end up with shutting down eth0, so the server
becomes unusable (I lost my SSH connection).

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet static

auto eth2
iface eth2 inet static

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.

  ifupdown not working when multiple interfaces

Status in “ifupdown” package in Ubuntu:

Bug description:
  Ubuntu Server 12.04
  ifup hangs when trying to start interface (only when using dhclient)
  ifdown is complaining that interfaces is not in '/run/network/ifstate', and so refusing to stop it.
  BUT worse ifdown eth2 will shutdown eth0, and so I lose connection over eth0 SSH.
  After reboot, server cannot setup network.

  Problem lies when ifup is forking to dhclient and it gets also messed
  up with is '/run/network' files. When using only one interface
  everything works fine but when two or more interfaces are setup it
  becomes buggy, for now I replaces ifup with ifconfig in

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list