From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Postmaster <iptables-pmd0052@promind.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: question about -t nat
Date: Sat, 19 Jun 2004 13:18:48 -0400 [thread overview]
Message-ID: <1087665527.7106.15.camel@localhost> (raw)
In-Reply-To: <000501c4561d$0495e830$6900a8c0@W2K>
On Sat, 2004-06-19 at 12:46, Postmaster wrote:
> hello list-users,
>
> i want clean up my pre- and postrouting chains with rules like this:
>
> iptables -t nat -A PREROUTING -i eth0 -j first_group
> iptables -t nat -A PREROUTING -i eth1 -j second_group
>
> iptables -t nat first_group -s a.b.c.d -d x/y -p tcp --sport
> 1024:65535 --dport 10001 -j DNAT --to-destination 1.2.3.4:25
> iptables -t nat second_group -s a.b.c.d -d x/y -p tcp --sport
> 1024:65535 --dport 10002 -j DNAT --to-destination 4.5.6.7:25
>
> is there any modul which makes this possible?
<snip>
I'm not sure I see the problem other than adding an action to the user
defined chain rules such as -A or -I - John
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
next prev parent reply other threads:[~2004-06-19 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 16:46 question about -t nat Postmaster
2004-06-19 17:18 ` John A. Sullivan III [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-19 17:57 Postmaster
2004-06-19 18:38 ` John A. Sullivan III
2004-06-19 19:54 ` Postmaster
2004-06-19 22:18 ` John A. Sullivan III
2004-06-19 22:40 ` Daniel Wittenberg
2004-06-19 23:21 ` John A. Sullivan III
2004-06-19 23:25 ` Postmaster
2004-06-19 23:53 Jan Brand (Postmaster)
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=1087665527.7106.15.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=iptables-pmd0052@promind.de \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox