netdev - A question about setting the net device for multicast forwarding in IPv4 and in IPv6

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-next>] [day] [month] [year] [list]

Message-ID: <31436f4a0805060638o2f97e3d7v8355fb678454da47@mail.gmail.com>
Date:	Tue, 6 May 2008 16:38:04 +0300
From:	"David Shwatrz" <dshwatrz@...il.com>
To:	netdev@...r.kernel.org,
	"YOSHIFUJI Hideaki / 吉藤英明" 
	<yoshfuji@...ux-ipv6.org>
Subject: A question about setting the net device for multicast forwarding in IPv4 and in IPv6

Hi,
  I had noticed that in IPV4 we set the net device for multicast
forwarding in case
it is not already configured so, when the user space app calls
setsockopt() with MRT_INIT;
this is done by calling IPV4_DEVCONF_ALL(sock_net(sk), MC_FORWARDING)++;
in ip_mroute_setsockopt(); (net/ipv4/ipmr.c).

On the other hand, the parallel method in IPv6 does **not** performs
such action, as can be seen
from ip6_mroute_setsockopt() in net/ipv6/ip6mr.c.

My question is : is there any special for it to be so? (In case it
should be also in IPv6, I will happy to send such a patch).

Best Regards,
DS
--
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