Public bug reported:
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
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
--
Bonding configuration in /etc/network/interfaces is altered by unknown process
https://bugs.launchpad.net/bugs/416562
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
