All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tiaan Wessels <tiaan@netsys.co.za>
To: netfilter@vger.kernel.org
Subject: ROUTE module problem
Date: Thu, 18 Oct 2007 07:07:27 +0000	[thread overview]
Message-ID: <4717062F.6030907@netsys.co.za> (raw)

Hi,

I have the need to duplicate UDP packets arriving at a machine. They 
need to be duplicated and sent of to both the original recipient and a 
new recipient.
After some reading I came to the conclusion the     -j ROUTE --tee    
option to iptables is the way to go. Getting this to work for a novice 
like me seems to be impossible.
Doing a man on my FC5 system shows --tee to be there under the ROUTE 
extension and I quote from the man page
'iptables can use extended target modules: the following are included in 
the standard distribution'
however using iptables results in

[root@nst2 ~]# /sbin/iptables -A PREROUTING -t mangle -p udp -d 
192.168.3.77 --dport 9090 -j ROUTE --tee
iptables v1.3.5: Unknown arg `--tee'

locate libipt_ROUTE.so yields nothing which makes me believe the man 
page was talking bollocks when claiming the extensions to be part of the 
'standard distribution'

After further reading I came to the conclusion patch-o-matic needed to 
be used to install the ROUTE module. going to netfilter extensions HOWTO 
I see I have to get the latest update from CVS like in so

cvs -d :pserver:cvs@pserver.netfilter.org:/cvspublic login


but when I do this I get

[root@nst2 ~]# cvs -d :pserver:cvs@pserver.netfilter.org:/cvspublic login
Logging in to :pserver:cvs@pserver.netfilter.org:2401/cvspublic
CVS password:
cvs [login aborted]: connect to 
pserver.netfilter.org(213.95.27.115):2401 failed: Connection refused

so I really am giving up now after waisting enough time ... so any 
experts out there willing to take me by the hand ??????

thanks


                 reply	other threads:[~2007-10-18  7:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4717062F.6030907@netsys.co.za \
    --to=tiaan@netsys.co.za \
    --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 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.