[Bug 678425] Re: alias network interfaces sometimes dont start on boot

[Clint Byrum]

Also I was recently shown an alternative way to add addresses to
interfaces which may become the recommended way:

iface eth0 inet manual
  up   ip link    set   dev $IFACE up
  up   ip address add   dev $IFACE brd + x.x.x.x/26
  up   ip address add   dev $IFACE brd + 192.168.155.20/24
  up   ip address add   dev $IFACE brd + 192.168.155.21/24
  up   ip address add   dev $IFACE brd + 192.168.155.211/24
  down ip address flush dev $IFACE
  down ip link    set   dev $IFACE down

This leverages iproute2 and is probably the more straightforward way to
do complex setups. Note that I haven't tested this, it was just an idea
somebody else showed me.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/678425

Title:
  alias network interfaces sometimes dont start on boot

Status in ifupdown:
  New
Status in “ifupdown” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: upstart

  Hello,
  I have 4 virtual network interfaces configured for autostart on two of my servers. All of them are bound to the same network interface eth0 and have static IP addresses. When I restart the server, sometimes some of them is down after restart and I have to start it manually with ifup. The physical network interface is always up correctly after reboot.
  It does not happen after every reboot and it is not always the same virtual interface which is left down.
  I cannot find any relevant information in syslog regarding this issue. This is a big problem as I have to manually check if all interfaces are running after every restart. 
  I dont know what other info/logfiles should I provide but please feel free to ask.
  Does anyone have similar issue?
  My distro is Ubuntu 10.04.1 Server 64bit.

  Thanx
  Roman Smid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ifupdown/+bug/678425/+subscriptions