From: Abhishek Singh <abhishek@abhishekonline.info>
To: netfilter-devel@vger.kernel.org
Subject: ROUTE patch
Date: Tue, 24 Feb 2009 14:29:57 +0530 [thread overview]
Message-ID: <c122d6890902240059j540fc8dcl529129d7bc5006fe@mail.gmail.com> (raw)
Hi Everyone
A long time ago, iptables used to have a ROUTE extension. This option
adds a `ROUTE' target, which enables you to setup unusual routes. For
example, the ROUTE lets you route a received packet through an
interface or towards a host, even if the regular destination of the
packet is the router itself. The ROUTE target is also able to change
the incoming interface of a packet.
This extension was discontinued sometime in 2007 and there as of now,
such a ROUTE target does not exist. I found it rather useful and
upgraded its source code to work with the latest kernel and the latest
iptables code also.
What I would like to know is that if someone would like to add it to
the main iptables tree and the patchomatic repository. I am not sure
how to go about it. If someone is interested, please let me know. I
shall contribute the code and if would be happy to incorporate review
comments by other developers.
Regards
Abhishek
next reply other threads:[~2009-02-24 8:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 8:59 Abhishek Singh [this message]
2009-02-24 9:35 ` ROUTE patch Jan Engelhardt
2009-02-24 13:41 ` Patrick McHardy
2009-02-24 15:30 ` Jan Engelhardt
2009-02-24 15:33 ` Patrick McHardy
2009-02-25 3:14 ` Abhishek Singh
2009-02-25 10:00 ` TEE patch [was: ROUTE patch] Jan Engelhardt
2009-02-25 10:19 ` Patrick McHardy
2009-02-25 10:26 ` Jan Engelhardt
2009-02-25 10:29 ` Patrick McHardy
2009-02-25 14:57 ` Jan Engelhardt
2009-02-26 10:03 ` Patrick McHardy
2009-03-07 0:26 ` 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=c122d6890902240059j540fc8dcl529129d7bc5006fe@mail.gmail.com \
--to=abhishek@abhishekonline.info \
--cc=netfilter-devel@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).