On Thu, Mar 01, 2007 at 02:25:19PM -0500, Brian Haley wrote: > Jay Vosburgh wrote: > >>My only concern is that this code assumes all mcast addresses stored in > >>dev->mc-list list are for ipv4 igmp mcast addresses and nothing was done > >>for ipv6. > >> > >>But this is much better than what we have now, so... > > > > Agreed, but there's no IPv6 support anywhere in bonding at > >present (for unicast or multicast), so this isn't really a loss. > > So forgive my naive question, but what would it take to make IPv6 work? > I know DAD fails on a test setup I have, but I haven't dug-into why > this is (I can guess), and I'd like to see it working. I'm willing to > help, even if just to get it limping along. >
Brian, If we are easily able to differentiate between the multicast addresses in the mc_list as to which are for ipv4 and which are for ipv6 then it would be easy to call-out to something in the ipv6 mcast code when needed instead of always calling out to ipv4 code. -andy - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
