From: "Javier Gálvez Guerrero" <javier.galvez.guerrero@gmail.com>
To: netfilter@vger.kernel.org
Subject: Duplicated multicast packets with -j ROUTE --tee
Date: Tue, 17 Jun 2008 11:43:41 +0200 [thread overview]
Message-ID: <145d4e1a0806170243m1eb8a6bds888f8e9bd4146d92@mail.gmail.com> (raw)
Hi everyone,
I'm a complete newbie with iptables. I've read some tutorials from
netfilters.org in order to have a look about how to proceed. I'm
generating a multicast flow and, in order to take some research
results, I would like to duplicate the packets in the source computer
through the ethernet interface.
I'm working in a Debian machine with kernel 2.6.18-6-686 and iptables
version 1.3.6. I have done some research with google and, eventually,
I've tried this:
# iptables -t mangle -A OUTPUT -d 239.255.1.0/24 -o eth0 -j ROUTE
--tee --oif eth0
but I obtain:
iptables: No chain/target/match by that name
Besides that, if I try the same without specifying what ROUTE should do:
# iptables -t mangle -A OUTPUT -d 239.255.1.0/24 -o eth0 -j ROUTE
I get:
iptables v1.3.6: ROUTE target: oif, iif or gw option required
Try `iptables -h' or 'iptables --help' for more information.
Then, I think that the ROUTE target is included in the kernel, so I
suppose there's no need to apply a patch and recompile the kernel but
I don't know what to do in order to succeed in this.Hi everyone,
Anyway, I would like to get some help for more experienced users or
anyone who has dealed with this issue. Any help would be much
appreciated.
Thank you all,
Javi
PS: Some issues with formatted text. Sorry.
next reply other threads:[~2008-06-17 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 9:43 Javier Gálvez Guerrero [this message]
2008-06-17 13:39 ` Duplicated multicast packets with -j ROUTE --tee Javier Gálvez Guerrero
2008-06-17 14:40 ` Jan Engelhardt
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=145d4e1a0806170243m1eb8a6bds888f8e9bd4146d92@mail.gmail.com \
--to=javier.galvez.guerrero@gmail.com \
--cc=netfilter@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