From: David Miller <davem@davemloft.net>
To: yoshfuji@linux-ipv6.org
Cc: okir@suse.de, netdev@vger.kernel.org, jbeulich@suse.de
Subject: Re: [RFC IPv6] Disabling IPv6 autoconf
Date: Tue, 29 Aug 2006 02:54:00 -0700 (PDT) [thread overview]
Message-ID: <20060829.025400.37356422.davem@davemloft.net> (raw)
In-Reply-To: <20060829.183426.52410264.yoshfuji@linux-ipv6.org>
From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Date: Tue, 29 Aug 2006 18:34:26 +0900 (JST)
> Further analysis is needed, but one idea is to skip
> addrconf_dev_config() if !(dev->flags & IFF_MULTICAST).
Yes, it is logical because without multicast IPV6 cannot
work correctly.
But from another perspective (I assume these bridged Xen devices use
ARPHRD_ETHER, do they?) a device with ARPHRD_ETHER and cleared
IFF_MULTICAST flag seems potentially problematic. How many other
things break over such a device?
next prev parent reply other threads:[~2006-08-29 9:54 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 [this message]
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
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=20060829.025400.37356422.davem@davemloft.net \
--to=davem@davemloft.net \
--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).