From: Tomasz Chmielewski <mangoo@wpkg.org>
To: David Lamparter <equinox@diac24.net>
Cc: netdev@vger.kernel.org
Subject: Re: bonding and IPv6 "doesn't work"?
Date: Tue, 12 Jul 2011 18:25:16 +0200 [thread overview]
Message-ID: <4E1C756C.2010700@wpkg.org> (raw)
In-Reply-To: <20110712161455.GD909183@jupiter.n2.diac24.net>
On 12.07.2011 18:14, David Lamparter wrote:
> On Tue, Jul 12, 2011 at 06:05:41PM +0200, Tomasz Chmielewski wrote:
>> I make a bond0 of two interfaces, eth0 and eth1.
>
> What kind of device do you have on the other side of those links?
It's a virtual machine.
So, a bridge of the host.
I know it doesn't make much sense to set up bonding in a virtual
machine, but I'm trying to determine what possible problems I might have
in a production environment (and got stuck at the very beginning).
IPv4 bonding works fine in this setup.
>> bond0: IPv6 duplicate address 2a01:4f8:120:14c4::1247 detected!
> [...]
>> However if I start bonding with just one interface, add IPv6 address to
>> it, then use ifenslave to add a second interface, I'm able to reach the
>> hosts in the internet.
>
> Yeah, when you add the IPv6 address, IPv6 ND does its job and announces
> your presence/does DAD.
Shouldn't this disable DAD? Or am I confusing something here?
net.ipv6.conf.eth0.accept_dad = 0
net.ipv6.conf.eth1.accept_dad = 0
> Your bonding peer is probably looping those
> packets back on the other link, most likely because...
>
>> Bonding Mode: load balancing (round-robin)
>
> ... most likely because you maybe have a switch on the other side, and
> that switch expects you to do 802.3ad?
It's a virtual machine, so the host shouldn't know or care much about
802.3ad (I think!).
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2011-07-12 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 16:05 bonding and IPv6 "doesn't work"? Tomasz Chmielewski
2011-07-12 16:14 ` David Lamparter
2011-07-12 16:25 ` Tomasz Chmielewski [this message]
2011-07-12 16:36 ` David Lamparter
2011-07-12 17:15 ` Chris Friesen
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=4E1C756C.2010700@wpkg.org \
--to=mangoo@wpkg.org \
--cc=equinox@diac24.net \
--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.