netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Haley <brian.haley@hp.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>,
	Alex Sidorenko <alexandre.sidorenko@hp.com>,
	Jeff Garzik <jeff@garzik.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Bonding and Neighbour Discovery on IPv6-only devices
Date: Wed, 24 Sep 2008 17:07:53 -0400	[thread overview]
Message-ID: <48DAAC29.6000108@hp.com> (raw)
In-Reply-To: <7958.1222288188@death.nxdomain.ibm.com>

Jay Vosburgh wrote:
> Vlad Yasevich <vladislav.yasevich@hp.com> wrote:
> [...]
>> It doesn't.  What appears to happen in the active-backup case the MLD reports
>> are not generated on all of the slave devices, just the active one.  Thus the
>> switch knows only about the active device.
> 
> 	This behavior is by design.  Previously, it worked the other way
> (every slave did IPv6 addrconf stuff, etc), but that confused the
> switches because they'd snoop the addrconf traffic whenever a backup
> slave came up, and update the switch forwarding table.
> 
>> When you force the failover, no reports happen because the device believes that
>> the MLD group was already reported.  Thus there needs to be some trigger after
>> the failover to tell the switch that the mac address and multicast group have
>> moved to a different port.
> 
> 	Yes, there needs to be an ipv6 equivalent of the gratuitous ARP
> and IGMP rejoin that's done for ipv4.  I haven't figured out how to
> accomplish that yet; suggestions are welcome.

I have a patch that does it, just doing some final testing before 
sending it out, hopefully later today...

-Brian

  reply	other threads:[~2008-09-24 21:07 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
2008-09-24 16:58     ` Vlad Yasevich
2008-09-24 20:29       ` Jay Vosburgh
2008-09-24 21:07         ` Brian Haley [this message]
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=48DAAC29.6000108@hp.com \
    --to=brian.haley@hp.com \
    --cc=alexandre.sidorenko@hp.com \
    --cc=fubar@us.ibm.com \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=vladislav.yasevich@hp.com \
    /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).