Diff: LinuxEthernetBonding

Differences between current version and predecessor to the previous major change of LinuxEthernetBonding.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 3 Last edited on Saturday, February 25, 2006 3:17:11 pm by MichaelJager
Older page: version 2 Last edited on Sunday, January 22, 2006 9:17:55 am by DanielLawson Revert
@@ -50,8 +50,10 @@
 ifconfig bond0 netmask up 
 ifenslave bond0 eth0 
 ifenslave bond0 eth1 
+During a setup I did recently (February 2006) using active-backup, I had to change the MAC address of the interface that was ifenslaved second to be the same as the first. It seemed that something weird was happening like the second interface would answer an ARP request for an IP address, and provide the MAC address of the bridge, but the machine never got packets, because it wouldn't accept packets for anything other than the MAC of the second interface. I didn't investigate further, it could have been something I was doing wrong. -- MichaelJager (IsomerMadeMeDoThis)  
 Your distribution will possibly have native interface control support for creating bonded interfaces. Check your manual pages. RedHat and SuSE (and derivatives) have native support; debian doesn't appear to. 
 An example of how to do this within debian is as follows: 
@@ -78,10 +80,12 @@
 You can specify VLAN interfaces on top of a bonded interface. Simply assign the bond0 interface no IP address (or, and then you can use the bond0 interface as the physical device for the VLAN interface. Refer to your distribution documentation on how to setup vlans within your network configuration. 
+I've done this, and it works well. I wanted to use bridging at let STP work out which interface to put into forwarding, and which to put into blocking, but the bridging driver didn't work with per-VLAN spanning tree; as a result I ended up using bonding in active-backup mode. -- MichaelJager  
 * Linux kernel documentation, Documentation/networking/bonding.txt