From: Jay Vosburgh <fubar@us.ibm.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Alex Sidorenko <asid@hp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Bonding and Neighbour Discovery on IPv6-only devices
Date: Mon, 15 Sep 2008 11:16:08 -0700 [thread overview]
Message-ID: <2540.1221502568@death.nxdomain.ibm.com> (raw)
In-Reply-To: <20080915180015.GB1078@havoc.gtf.org>
Jeff Garzik <jeff@garzik.org> wrote:
>On Mon, Sep 15, 2008 at 01:35:16PM -0400, Alex Sidorenko wrote:
[...]
>> 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...
The fix that just went in has to do with traffic balancing in
alb/tlb modes; this problem has to do with the lack of an IPv6
equivalent to a gratuitous ARP during a user-induced failover.
I'm looking into this; it might be simple to fix.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next prev parent reply other threads:[~2008-09-15 18:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 17:35 Bonding and Neighbour Discovery on IPv6-only devices Alex Sidorenko
2008-09-15 18:00 ` Jeff Garzik
2008-09-15 18:16 ` Jay Vosburgh [this message]
2008-09-15 18:16 ` Alex Sidorenko
2008-09-24 16:58 ` Vlad Yasevich
2008-09-24 20:29 ` Jay Vosburgh
2008-09-24 21:07 ` Brian Haley
2008-09-25 2:46 ` [RFC] bonding: add better ipv6 failover support Brian Haley
2008-09-25 15:07 ` Jay Vosburgh
2008-09-25 15:42 ` Brian Haley
2008-10-01 5:53 ` Simon Horman
2008-10-01 13:24 ` Brian Haley
2008-10-01 13:36 ` David Miller
2008-09-26 18:51 ` David Stevens
2008-09-26 19:09 ` Jay Vosburgh
2008-09-26 19:28 ` Brian Haley
2008-09-26 19:55 ` Vlad Yasevich
2008-09-26 19:46 ` Vlad Yasevich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2540.1221502568@death.nxdomain.ibm.com \
--to=fubar@us.ibm.com \
--cc=asid@hp.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).