netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Bieringer <pb@bieringer.de>
To: Pekka Savola <pekkas@netcore.fi>
Cc: David Miller <davem@davemloft.net>,
	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 13:13:58 +0200	[thread overview]
Message-ID: <44F42176.1000701@bieringer.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0608291348520.25442@netcore.fi>

Pekka Savola schrieb:
> On Tue, 29 Aug 2006, David Miller wrote:
>> 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?
> 
> It's not obvious that IFF_MULTICAST is good enough.  IMHO, you should be
> able to run addrconf on non-multicast interfaces as well (e.g.,
> point-to-point interfaces, tunnels in particular).

Hmm, at least on RHEL4 (2.6.9):

1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
4: sit0: <NOARP> mtu 1480 qdisc noop
5: sit1@NONE: <POINTOPOINT,NOARP,UP> mtu 1480 qdisc noqueue
6: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1492 qdisc pfifo_fast qlen 3
8: tun6to4@NONE: <NOARP,UP> mtu 1480 qdisc noqueue


And contributed from FC5:

5: vmnet8: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen
1000
7: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc
pfifo_fast qlen 100


ppp0, tun0 has IFF_MULTICAST set, so not an issue.

> It seems that current code already excludes IFF_NOARP interfaces though.

So 6-in-4 tunnels are already except.


Don't wonder about Flag "10000", missing support in "ip", already
reported https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202199 and
fixed in rawhide.


Just my 2 cents,

	Peter
-- 
Dr. Peter Bieringer                     http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D                       mailto:pb@bieringer.de
Deep Space 6 Co-Founder and Core Member  http://www.deepspace6.net/
OpenBC                    http://www.openbc.com/hp/Peter_Bieringer/
Personal invitation to OpenBC  http://www.openbc.com/go/invita/3889

  parent reply	other threads:[~2006-08-29 11:14 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 [this message]
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=44F42176.1000701@bieringer.de \
    --to=pb@bieringer.de \
    --cc=davem@davemloft.net \
    --cc=jbeulich@suse.de \
    --cc=netdev@vger.kernel.org \
    --cc=okir@suse.de \
    --cc=pekkas@netcore.fi \
    --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).