Re: Bonding and Neighbour Discovery on IPv6-only devices
From: Alex Sidorenko <hidden>
Date: 2008-09-15 18:16:51
On September 15, 2008 02:00:15 pm Jeff Garzik wrote:
On Mon, Sep 15, 2008 at 01:35:16PM -0400, Alex Sidorenko wrote:quoted
Hello, I suspect that there are some problems while switching slaves manually on IPv6-only bonds. I have tested that this does not work on 2.6.18 kernel (RHEL5). I looked at recent sources (2.6.26) and even though there were multiple changes in bonding code, I still don't see how this could work. Testing setup ------------- Two ethernets enslaved (eth2 and eh3), active-backup bond has IPv6-only address (no IPv4) Everything works fine, but if we switch the slave doing # ifenslave -c bond0 eth3 the incoming ping6 to this host stops for up to several minutes (waiting until the switch updates its caches).We _just_ put in an IPv6 fix, FWIW...
Hi Jeff, do you mean the patch for ALB/TLB bonds? I looked at it but I still don't understand how this helps for active-backup case. Alex -- ------------------------------------------------------------------ Alexandre Sidorenko email: alexs@hplinux.canada.hp.com Global Solutions Engineering: Unix Networking Hewlett-Packard (Canada) ------------------------------------------------------------------