Package: ifenslave-2.6 Version: 1.1.0-14 Severity: important Tags: patch
While building the following situation I receive my own broadcast traffic on the backup interface. +------+ +----+ |switch|---|eth0|----+ +------+ +----+ | | +-----+ +---------+ +-----+ | |bond0|---|bond0.101|---|br101| | +-----+ +---------+ +-----+ +------+ +----+ | |switch|---|eth1|----+ +------+ +----+ With every arp packet send out to the network I get the error: 'bond0.101: received packet with own address as source address'. When removing the bridge from the setup the error goes away. But, sniffing with tshark still shows duplicate arp packets comming in. Doing an ifconfig down/up on one of the slave interfaces fixes the issue. The problem does not exist in ifenslave 1.1.0-10 but starts happening on 1.1.0-14. I think it has to do with the way the bond is initialized. With 1.1.0-10 the bond interface gets fully configured before adding the slaves and with 1.1.0-14 the slaves get added first. The following patch seems to fix the problem on my test setup. --- debian/pre-up 2009-12-07 11:35:55.000000000 +0100 +++ debian.new/pre-up 2009-12-07 13:51:31.000000000 +0100 @@ -125,5 +125,5 @@ [ -z "$BOND_MASTER$BOND_SLAVES" ] && exit add_master -enslave_slaves setup_master +enslave_slaves Regards, Sander -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
