netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: thomas.goff@boeing.com
Cc: netdev@vger.kernel.org, fred.l.templin@boeing.com
Subject: Re: [PATCH] IPv6 multicast routing
Date: Tue, 27 Jan 2009 22:39:02 -0800 (PST)	[thread overview]
Message-ID: <20090127.223902.45013943.davem@davemloft.net> (raw)
In-Reply-To: <20090120200248.GA13928@boeing.com>

From: Tom Goff <thomas.goff@boeing.com>
Date: Tue, 20 Jan 2009 12:02:48 -0800

>   - Enable/disable IPv6 multicast forwarding on the corresponding
>     interface when a routing daemon adds/removes a multicast virtual
>     interface.

Since Hideaki-san is being unresponsive I looked at this patch again
so I can apply it, or at least part of it, to get the bugs fixed.

I disagree with his objection to the mc_forwarding changes here, they
are correct and in fact desirable.  They are desirable since without
this we have yet another disconnect between ipv4 and ipv6 behavior.

We already have way too many of those.

Every time I notice a behavior difference between our ipv4 and ipv6
stack I almost believe there is an active conspiracy to make the
transition to ipv6 as difficult as possible :-)

So I'm going to apply this patch as-is, with the addition of making
the mc_forwarding sysctl read-only (perms 0444) as it is in ipv4.

      parent reply	other threads:[~2009-01-28  6:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 20:02 [PATCH] IPv6 multicast routing Tom Goff
2009-01-21  1:04 ` YOSHIFUJI Hideaki / 吉藤英明
2009-01-22 23:30   ` Goff, Thomas
2009-01-26  2:15     ` David Miller
2009-01-27  5:31       ` David Miller
2009-01-28  6:39 ` David Miller [this message]

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=20090127.223902.45013943.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=fred.l.templin@boeing.com \
    --cc=netdev@vger.kernel.org \
    --cc=thomas.goff@boeing.com \
    /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).