[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48DAAC29.6000108@hp.com>
Date: Wed, 24 Sep 2008 17:07:53 -0400
From: Brian Haley <brian.haley@...com>
To: Jay Vosburgh <fubar@...ibm.com>
CC: Vlad Yasevich <vladislav.yasevich@...com>,
Alex Sidorenko <alexandre.sidorenko@...com>,
Jeff Garzik <jeff@...zik.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Bonding and Neighbour Discovery on IPv6-only devices
Jay Vosburgh wrote:
> Vlad Yasevich <vladislav.yasevich@...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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists