From: David Miller <davem@davemloft.net>
To: Thomas.Goff@boeing.com
Cc: yoshfuji@linux-ipv6.org, netdev@vger.kernel.org,
Fred.L.Templin@boeing.com
Subject: Re: [PATCH] IPv6 multicast routing
Date: Sun, 25 Jan 2009 18:15:10 -0800 (PST) [thread overview]
Message-ID: <20090125.181510.81366979.davem@davemloft.net> (raw)
In-Reply-To: <21C34AA2609529459A85739E2952066904A9670D@XCH-NW-9V1.nw.nos.boeing.com>
From: "Goff, Thomas" <Thomas.Goff@boeing.com>
Date: Thu, 22 Jan 2009 15:30:38 -0800
> On Wed, Jan 21, 2009 at 10:04:31AM +0900, YOSHIFUJI Hideaki / 吉藤英明 wrote:
>
> > > - Enable/disable IPv6 multicast forwarding on the corresponding
> > > interface when a routing daemon adds/removes a multicast virtual
> > > interface.
> :
> > However, I believe configuring forwarding is user's responsibility
> > and I'm not in favor of managing mc_forwarding automatically.
> >
> > If we go your way, we need to make the proc interface read-only, but
> > you know, they will become non-"conf" interface. :-(
> > And, well, we will introduce another possible overflow/underflow here...
> >
> > Another thought was to allow non-VIF routing settings (or manual settings).
> >
> > So, I decided to drop that bits.
>
> Thanks for looking it over.
>
> I think your approach to handling mc_forwarding makes sense, although
> it differs from the IPv4 behavior. In any case, it looks like the
> current IPv4 and IPv6 multicast routing code does not consider an
> interface's mc_forwarding value at all.
Thanks guys.
Hideaki-san, did you queue this patch up or do you want me to
apply it with the mc_forwarding counter bumps removed?
These are bug fixes so I'd like to see this in the tree soon.
next prev parent reply other threads:[~2009-01-26 2:15 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 [this message]
2009-01-27 5:31 ` David Miller
2009-01-28 6:39 ` David Miller
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=20090125.181510.81366979.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Fred.L.Templin@boeing.com \
--cc=Thomas.Goff@boeing.com \
--cc=netdev@vger.kernel.org \
--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).