From: "Andy Johnson" <johnsonzjo@gmail.com>
To: "David Shwatrz" <dshwatrz@gmail.com>
Cc: netdev@vger.kernel.org,
"YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Subject: Re: A question about setting the net device for multicast forwarding in IPv4 and in IPv6
Date: Mon, 12 May 2008 11:57:05 +0300 [thread overview]
Message-ID: <147a89290805120157y7af3ad9bge6ce23332b9040ca@mail.gmail.com> (raw)
In-Reply-To: <31436f4a0805060638o2f97e3d7v8355fb678454da47@mail.gmail.com>
Hello, David,
- I wanted to note that there is one more difference I had noted
between IPv4 and IPv6
regarding multicast forwarding:
- In IPv4, mc_forwarding is disabled by default (the value is 0). If
you will try to change it thus:
echo "1" > /proc/sys/net/ipv4/conf/eth0/mc_forwarding
you will get:
/proc/sys/net/ipv4/conf/eth0/mc_forwarding: Permission denied.
ls -al /proc/sys/net/ipv4/conf/eth0/mc_forwarding
will show:
-r--r--r-- 1 root root 0 ...
But:
chmod 666 /proc/sys/net/ipv4/conf/eth0/mc_forwarding
gives:
chmod 666 /proc/sys/net/ipv4/conf/eth0/mc_forwarding
chmod: changing permissions of
`/proc/sys/net/ipv4/conf/eth0/mc_forwarding': Operation not permitted
User space daemons (like xorp) will set
/proc/sys/net/ipv4/conf/all/mc_forwarding to 1
(because they call setsockopt with MRT_INIT, which calls
IPV4_DEVCONF_ALL(sock_net(sk), MC_FORWARDING)++;
in ip_mroute_setsockopt(), as you mentioned.
In IPV6, this does not happen.
In IPV6, Multicast Routing is also disabled by default.
**But **
echo "1" > /proc/sys/net/ipv6/conf/all/mc_forwarding
**does** work and **does not** give an error (as in IPV4).
I wonder what is the reason for it ? Or maybe it should be changed to
have the same behaviour both in IPV6 and IPV4?
Regards,
Andy
On Tue, May 6, 2008 at 4:38 PM, David Shwatrz <dshwatrz@gmail.com> wrote:
> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-05-12 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 13:38 A question about setting the net device for multicast forwarding in IPv4 and in IPv6 David Shwatrz
2008-05-12 8:57 ` Andy Johnson [this message]
2008-05-12 11:08 ` Rami Rosen
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=147a89290805120157y7af3ad9bge6ce23332b9040ca@mail.gmail.com \
--to=johnsonzjo@gmail.com \
--cc=dshwatrz@gmail.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).