I hope this will be useful for those of you out there who want to configure the bonding driver. I am not going to cover 802.3ad as i do not have a managed switch yet.
You have to install
ifenslave, it is a tool to attach and detach slave network interfaces to a bonding device.
sudo apt-get install ifenslave
Module Alias Configuration
create the following file:
sudo vi /etc/modprobe.d/bonding.conf
with the following contents
alias bond0 bonding options bonding mode=0 miimon=100
The bonding options (except Hardy) can also be configured at network interface level in /etc/network/interfaces, see further below for an example. If you wish you can go further and lock put in aliases for your Ethernet cards, but as these days everything seems to be locked to the mac address I haven't mode=0 (balance-rr) Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance. mode=1 (active-backup) Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode. mode=2 (balance-xor) XOR policy: Transmit based on [(source MAC address XOR'd with destination MAC address) modulo slave count]. This selects the same slave for each destination MAC address. This mode provides load balancing and fault tolerance. mode=3 (broadcast) Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance. mode=4 (802.3ad) IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification. Pre-requisites: 1. Ethtool support in the base drivers for retrieving
the speed and duplex of each slave. 2. A switch that supports IEEE 802.3ad Dynamic link
aggregation. Most switches will require some type of configuration to enable 802.3ad mode. mode=5 (balance-tlb) Adaptive transmit load balancing: channel bonding that does not require any special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave. Prerequisite: Ethtool support in the base drivers for retrieving the speed of each slave. mode=6 (balance-alb) Adaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server. The most used are the first four mode types...
now we need to create some entries in our network configuration.
sudo vi /etc/network/interfaces
Have a look at
/usr/share/doc/ifenslave-2.6/README.Debian. Your config file could look something like this
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface #auto eth0 #iface eth0 inet dhcp auto bond0 iface bond0 inet static address 192.168.1.10 gateway 192.168.1.1 netmask 255.255.255.0 slaves eth0 eth1 bond-mode 4 bond-miimon 100
Some older howto's sometimes mention another method to configure the bond
pre-up modprobe bonding up ifenslave bond0 eth1 eth2 pre-down ifenslave bond0 -d eth1 eth2 post-down rmmod bonding
This method has some downturns. First, loading and unloading the module through pre-up and post-down statements is not necessary, as the loading already happens in the modprope.d config, and it might even be unwanted in the case were one has multiple bonds configured, which would (try to) unload the module after bringing one bond down, whilst it still being in use for another one. Secondly, configuring the bond (ifenslave bond0 eth1 eth2) in the (post-)up statements didn't work for me: it seemed (post-)up happens after configuring an ip, but at that time the bond is not configured yet, and configuring the ip results in an error.