From: David Lamparter <equinox@diac24.net>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: David Lamparter <equinox@diac24.net>, netdev@vger.kernel.org
Subject: Re: bonding and IPv6 "doesn't work"?
Date: Tue, 12 Jul 2011 18:36:02 +0200 [thread overview]
Message-ID: <20110712163602.GE909183@jupiter.n2.diac24.net> (raw)
In-Reply-To: <4E1C756C.2010700@wpkg.org>
On Tue, Jul 12, 2011 at 06:25:16PM +0200, Tomasz Chmielewski wrote:
> It's a virtual machine.
> So, a bridge of the host.
Just a bridge? No bonding device? You need to set it up on both sides...
> >> 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
Yes, you would need to set
net.ipv6.conf.bond0.accept_dad = 0
because eth0 and eth1 are not actually participating in the IPv6 stack.
(I'd recommend setting disable_ipv6=1 for them too)
However, you should not be getting that DAD error at all, it indicates
that broadcast/multicast packets that go out on eth0 are looped back on
eth1 (and vice versa). Your bonding setups on the host and the VM don't
seem to match each other.
-David
next prev parent reply other threads:[~2011-07-12 16:36 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
2011-07-12 16:36 ` David Lamparter [this message]
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=20110712163602.GE909183@jupiter.n2.diac24.net \
--to=equinox@diac24.net \
--cc=mangoo@wpkg.org \
--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 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).