From: Brian Haley <brian.haley@hp.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: Andy Gospodarek <andy@greyhouse.net>,
netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH 3/3] bonding: Improve IGMP join processing
Date: Thu, 01 Mar 2007 14:25:19 -0500 [thread overview]
Message-ID: <45E7289F.60406@hp.com> (raw)
In-Reply-To: <200703011705.l21H5Q22005750@death.nxdomain.ibm.com>
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
next prev parent reply other threads:[~2007-03-01 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 1:03 [PATCH 3/3] bonding: Improve IGMP join processing Jay Vosburgh
2007-03-01 16:49 ` Andy Gospodarek
2007-03-01 17:05 ` Jay Vosburgh
2007-03-01 19:25 ` Brian Haley [this message]
2007-03-01 19:43 ` Andy Gospodarek
2007-03-01 21:58 ` Jay Vosburgh
2007-03-06 19:55 ` Brian Haley
2007-03-06 20:39 ` Jay Vosburgh
2007-03-06 20:44 ` Andy Gospodarek
2007-03-06 22:32 ` David Stevens
2007-03-06 23:15 ` [Bonding-devel] " Jay Vosburgh
2007-03-07 0:45 ` David Stevens
2007-03-07 1:50 ` Andy Gospodarek
2007-03-07 3:21 ` David Stevens
2007-03-09 16:53 ` Andy Gospodarek
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=45E7289F.60406@hp.com \
--to=brian.haley@hp.com \
--cc=andy@greyhouse.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=jgarzik@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.