From: Stephen Hemminger <shemminger@osdl.org>
To: Olaf Kirch <okir@suse.de>
Cc: "YOSHIFUJI Hideaki / ?$B5HF#1QL@" <yoshfuji@linux-ipv6.org>,
netdev@vger.kernel.org, jbeulich@suse.de
Subject: Re: [RFC IPv6] Disabling IPv6 autoconf
Date: Tue, 29 Aug 2006 08:51:50 -0700 [thread overview]
Message-ID: <20060829085150.03fc9bb3@localhost.localdomain> (raw)
In-Reply-To: <20060829104418.GI1201@suse.de>
On Tue, 29 Aug 2006 12:44:18 +0200
Olaf Kirch <okir@suse.de> wrote:
> On Tue, Aug 29, 2006 at 06:34:26PM +0900, YOSHIFUJI Hideaki / ?$B5HF#1QL@ wrote:
> > > The attached tentative patch makes IPv6 autoconf depend on the
> > > availability of IFF_MULTICAST. This is admittedly a bit of a hack, but
> > > it makes sense, since DAD and router solicitation do rely on multicast.
> >
> > I disagree. The node MUST NOT assign live address on
> > that interface.
>
> I'm not sure I understand. The Xen bridge devices get fe:ff:ff:ff:ff:ff
> as MAC address. Which is a bit hackish, but that seems to be the way
> the Xen folks want to do it.
They should be using random_ether_addr() or putting some per instance
specific info into the address.
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2006-08-29 15:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 8:24 [RFC IPv6] Disabling IPv6 autoconf Olaf Kirch
2006-08-29 9:34 ` YOSHIFUJI Hideaki / 吉藤英明
2006-08-29 9:54 ` David Miller
2006-08-29 10:39 ` Herbert Xu
2006-08-29 10:45 ` Olaf Kirch
2006-08-29 10:55 ` Pekka Savola
2006-08-29 11:10 ` Olaf Kirch
2006-08-29 11:13 ` Peter Bieringer
2006-08-29 16:30 ` Alexey Kuznetsov
2006-08-29 10:44 ` Olaf Kirch
2006-08-29 15:51 ` Stephen Hemminger [this message]
2006-08-29 11:21 ` Hasso Tepper
2006-08-29 11:31 ` Peter Bieringer
2006-08-29 13:04 ` Herbert Xu
2006-08-29 13:59 ` Hasso Tepper
2006-08-30 0:12 ` Herbert Xu
2006-08-30 3:26 ` YOSHIFUJI Hideaki / 吉藤英明
2006-08-30 5:41 ` Hasso Tepper
2006-08-29 18:10 ` Thomas Graf
2006-08-29 20:00 ` Olaf Kirch
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=20060829085150.03fc9bb3@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=jbeulich@suse.de \
--cc=netdev@vger.kernel.org \
--cc=okir@suse.de \
--cc=yoshfuji@linux-ipv6.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).