From: Stephen Hemminger <shemminger@vyatta.com>
To: Ang Way Chuang <wcang@sfc.wide.ad.jp>
Cc: netdev@vger.kernel.org
Subject: Re: commit 1faa4356 breaks IPv6 assignment on libvirtd
Date: Thu, 1 Sep 2011 08:51:26 -0700 [thread overview]
Message-ID: <20110901085126.76cdda54@nehalam.ftrdhcpuser.net> (raw)
In-Reply-To: <4E5F99E2.50301@sfc.wide.ad.jp>
On Thu, 01 Sep 2011 23:42:42 +0900
Ang Way Chuang <wcang@sfc.wide.ad.jp> wrote:
> Hi all,
>
> Commit 1faa4356 break IPv6 assignment on libvirtd. The configuration for my VM bridge network is as such:
>
> <network>
> <name>default</name>
> <forward mode='nat'/>
> <bridge name='virbr0' stp='on' delay='0' />
> <ip address='192.168.122.1' netmask='255.255.255.0'>
> <dhcp>
> <range start='192.168.122.2' end='192.168.122.254' />
> </dhcp>
> </ip>
> <ip family='ipv6' address='2001:d30:113:504::1' prefix='64'>
> </ip>
> </network>
>
> This configuration worked fine on kernel 2.6.38. Updating my distro kernel broke the setup. My colleague
> and I traced the problem and found that libvirtd failed because there wasn't any carrier on virbr0 interface
> due to the change introduced by that commit. How can this be fixed? Thanks in advance.
>
> Regards,
> Ang Way Chuang
The issue is that address is assigned to a bridge device with no ports.
IPv6 needs carrier to do duplicate address detection. Without any ports
the DAD will always succeed, and there is a possibility that when ports
are later added to the bridge the address actually is a duplicate.
A couple of possible options are:
1. Default to carrier on in bridge when there are no ports.
The downside with this is that IPv6 DAD is being fooled.
2. Change libvirt to allow turning off DAD. This is controlled
in kernel by writing 0 to /proc/sys/net/ipv6/conf/virbr0/accept_dad
next prev parent reply other threads:[~2011-09-01 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 14:42 commit 1faa4356 breaks IPv6 assignment on libvirtd Ang Way Chuang
2011-09-01 15:51 ` Stephen Hemminger [this message]
2011-09-02 5:57 ` Ang Way Chuang
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=20110901085126.76cdda54@nehalam.ftrdhcpuser.net \
--to=shemminger@vyatta.com \
--cc=netdev@vger.kernel.org \
--cc=wcang@sfc.wide.ad.jp \
/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.