netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Sidorenko <alexandre.sidorenko@hp.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Bonding and Neighbour Discovery on IPv6-only devices
Date: Mon, 15 Sep 2008 14:16:49 -0400	[thread overview]
Message-ID: <200809151416.49447.alexandre.sidorenko@hp.com> (raw)
In-Reply-To: <20080915180015.GB1078@havoc.gtf.org>

On September 15, 2008 02:00:15 pm Jeff Garzik wrote:
> On Mon, Sep 15, 2008 at 01:35:16PM -0400, Alex Sidorenko wrote:
> > 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)
------------------------------------------------------------------

  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
2008-09-15 18:16   ` Alex Sidorenko [this message]
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=200809151416.49447.alexandre.sidorenko@hp.com \
    --to=alexandre.sidorenko@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).