From: Jon Webb <jon_webb@binary-one.com>
To: netfilter-devel@lists.netfilter.org
Subject: multicast group traffic filtering
Date: Mon, 22 Dec 2003 01:54:04 -0800 [thread overview]
Message-ID: <3FE6BF3C.9030400@binary-one.com> (raw)
Hi everyone,
I am trying to think of a way to handle a multicast test network. We
have a setup that may require having a multicast router in a network
that contains other multicast activity. This extra router would only
want to route multicast traffic (control and data) for a specific
multicast group (our test group), ignoring all other multicast traffic
not part of that group. I know that the matching code is able to match
on a multicast packet type, but I need to match on a specific group. I
looked around the docs, but have been unable to find any kind of --match
type support for multicast group ID's or some sort of IGMP connection
tracking/handling. Is there something I missed? Can this be done with
existing tools? Or else, could this be easily constructed?
Thanks,
Jon
-------------
jon_webb@binary-one.com
jonwebb@soe.ucsc.edu
Computer Communications Research Group
University of California, Santa Cruz
next reply other threads:[~2003-12-22 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 9:54 Jon Webb [this message]
2003-12-22 11:03 ` multicast group traffic filtering Henrik Nordstrom
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=3FE6BF3C.9030400@binary-one.com \
--to=jon_webb@binary-one.com \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.