netdev - Re: [PATCH] IPv6 multicast routing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090121.100431.126366547.yoshfuji@linux-ipv6.org>
Date:	Wed, 21 Jan 2009 10:04:31 +0900 (JST)
From:	YOSHIFUJI Hideaki / 吉藤英明 
	<yoshfuji@...ux-ipv6.org>
To:	thomas.goff@...ing.com
Cc:	netdev@...r.kernel.org, fred.l.templin@...ing.com,
	yoshfuji@...ux-ipv6.org
Subject: Re: [PATCH] IPv6 multicast routing

In article <20090120200248.GA13928@...ing.com> (at Tue, 20 Jan 2009 12:02:48 -0800), Tom Goff <thomas.goff@...ing.com> says:

> This patch addresses the IPv6 multicast routing issues described
> below.  It was tested with XORP 1.4/1.5 as the IPv6 PIM-SM routing
> daemon against FreeBSD peers.
:
>   - Enable/disable IPv6 multicast forwarding on the corresponding
>     interface when a routing daemon adds/removes a multicast virtual
>     interface.

Thank you for tha patch!

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.

Other fixes seem okay.

--yoshfuji
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html