From: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
To: David Miller <davem@davemloft.net>
Cc: yoshfuji@linux-ipv6.org, okir@suse.de, netdev@vger.kernel.org,
jbeulich@suse.de
Subject: Re: [RFC IPv6] Disabling IPv6 autoconf
Date: Tue, 29 Aug 2006 20:30:03 +0400 [thread overview]
Message-ID: <20060829163003.GA30408@ms2.inr.ac.ru> (raw)
In-Reply-To: <20060829.025400.37356422.davem@davemloft.net>
Hello!
> Yes, it is logical because without multicast IPV6 cannot
> work correctly.
This is not quite true. IFF_BROADCAST is enough, it will work just
like IPv4.
Real troubles start only when interface is not IFF_BROADCAST and not
IFF_POINTOPOINT.
> IFF_MULTICAST flag seems potentially problematic. How many other
> things break over such a device?
Nothing should break. IFF_MULTICAST is an advisory flag, saying
mostly "You do not want to stream high bandwidth multicast video here".
So that, it can be used to block autoconfiguration.
It does not change the fact that Xen device makes something profoundly
wrong. IPv6 autoconfiguration is _auto_configuration. It is triggered
only for a few of media types, for which autoconfiguration is prescribed
by corresponding RFCs. Ethernet is one of them.
If Xen does not support the things, which are required for each
ethernet device, it should not be ARPHRD_ETHER. If it wants to pretend
to be ARPHRD_ETHER, it must support basic ethernet functions, which IMHO
is so _easy_, that the question does not even makes sense.
Alexey
next prev parent reply other threads:[~2006-08-29 16:30 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 [this message]
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=20060829163003.GA30408@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=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).