[Bug 416562] Re: Bonding configuration in /etc/network/interfaces is altered by unknown process

[Stéphane Graber]

ifupdown itself doesn't have any function to edit the interfaces file,
so it's not an ifupdown bug.

If you have NetworkManager installed, that may indeed be the problem, NM
is never supposed to touch /etc/network/interfaces but I honestly can't
remember its behaviour on 8.04.

Could you try with 10.04 and if it still happens, file a bug against NM?

** Changed in: ifupdown (Ubuntu)
       Status: New => Invalid

-- 
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/416562

Title:
  Bonding configuration in /etc/network/interfaces is altered by unknown
  process

Status in “ifupdown” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: ifupdown

  Disclaimer: This could very well be a NetworkManager or a udev rules
  thing or something else.

  We have an Ubuntu LTS box with 4 on board network controllers. We wish
  to bond eth0 and eth1 on one network and eth2 on another. With the
  following in /etc/network/interfaces, eth0 and eth1 successfully form
  a bond and eth2 is up on its network, however after booting eth1 is
  given the same IP address as the bonded interfaces and two default
  routes are created, one going through bond0 and the other through
  eth1. We have to 'ifconfig eth1 0.0.0.0' after booting to achieve the
  desired configuration. This is a production server so we can't
  experiment with packages above Hardy. I can't figure out what part of
  the Ubuntu networking stack is doing this.

  auto lo
  iface lo inet loopback

  auto bond0
  iface bond0 inet static
  	address w.x.y.z
  	netmask 255.255.255.0
  	broadcast w.x.y.255
  	gateway w.x.y.1
  	slaves eth0 eth1

  auto eth2
  iface eth2 inet static
  	address a.b.c.d
  	netmask 255.255.255.0
  	broadcast a.b.c.255

  We specify the following in /etc/modprobe.d/bonding:

  alias bond0 bonding
  options bonding mode=0 miimon=100 downdelay=200 updelay=200 fail_over_mac=0

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