Unfortunatly no, I replaced in '/etc/init/networking.conf' 'ifup -a'
with 'ifconfig eth0 192.168.1.100 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).
<pre>
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet static
network 192.168.2.0
netmask 255.255.255.0
gateway 192.168.2.1
address 192.168.2.1
broadcast 192.168.2.255
auto eth2
iface eth2 inet static
network 192.168.3.0
netmask 255.255.255.0
gateway 192.168.3.1
address 192.168.3.1
broadcast 192.168.3.255
</pre>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041356
Title:
ifupdown not working when multiple interfaces
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1041356/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
