-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Charles Steinkuehler wrote: | Hmm...other than upgrading your kernel, which would apparently fix your | problem, have you checked your arp settings on both ends? | | If the 10.0.3.3/24 IP on bond0 is somehow getting the MAC address of the | primary interface, and not the virtual MAC address of bond0, then taking | down eth1 would cause ping to stop working (at least until the arp-cache | entry timed out).
Bad form replying to myself, but I was reading through a current bonding.txt from the kernel documentation and found the following for mode=1: ~ In bonding version 2.6.2 or later, when a failover ~ occurs in active-backup mode, bonding will issue one ~ or more gratuitous ARPs on the newly active slave. ~ One gratuitous ARP is issued for the bonding master ~ interface and each VLAN interfaces configured above ~ it, provided that the interface has at least one IP ~ address configured. Gratuitous ARPs issued for VLAN ~ interfaces are tagged with the appropriate VLAN id. That could for sure explain why a newer kernel might appear to work better. The gratuitous arps would disguise the fact that the underlying network topology changed, making higher-level IP clients unaware of the switch. - -- Charles Steinkuehler [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIMx4hLywbqEHdNFwRAjAoAJ4ueTClmiXpZYzhvN7EZgx7N39yAwCdHP+X 7+/am7N5U7knbBTaKl609is= =KuVZ -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
