From: "Youngmin Kim" <blhole@venus.uos.ac.kr>
To: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: ipv6 multicast forwarding
Date: Fri, 25 Jul 2003 21:04:01 +0900 [thread overview]
Message-ID: <000301c352a4$d60594b0$1e6ef9cb@LocalHost> (raw)
I have a concern with ipv6 multicast!! But I don't know "linux
forwarding" well
I inserted 2 lines in ip6_mc_input()
....
if (ipv6_chk_mcast_addr(skb->dev, &hdr->daddr))
deliver =1;
>>if (ipv6_devconf.forwarding == 1)
>> ip6_mc_forward(skb, deliver);
if (deliver)
discard = 0;
ip6_input(skb);
}
......
I made ip6_mc_forward() which was modified from ip6_forward().
But it doesn't work...
How do I make ip6_mc_forward()?
I want simple ipv6 multicast forward...
When host receive multicast packet, host forward it without multicast
routing cache..
Then I will filter unneeded packets.
Nobody help me??
Thank you!!
next reply other threads:[~2003-07-25 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 12:04 Youngmin Kim [this message]
2008-10-23 22:11 IPv6 multicast forwarding Todd Hayton
2008-10-24 9:10 ` Alejandro Riveira Fernández
2008-10-24 10:12 ` Pekka Savola
2008-10-24 13:06 ` Todd Hayton
2008-10-26 10:26 ` Pekka Savola
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='000301c352a4$d60594b0$1e6ef9cb@LocalHost' \
--to=blhole@venus.uos.ac.kr \
--cc=linux-kernel@vger.kernel.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).