From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Daniel Wittenberg <daniel-wittenberg@starken.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: question about -t nat
Date: Sat, 19 Jun 2004 19:21:08 -0400 [thread overview]
Message-ID: <1087687267.2062.10.camel@localhost> (raw)
In-Reply-To: <1087684836.8013.3.camel@hawk.wittenberg.org>
On Sat, 2004-06-19 at 18:40, Daniel Wittenberg wrote:
> On Sat, 2004-06-19 at 17:18, John A. Sullivan III wrote:
> > On Sat, 2004-06-19 at 15:54, Postmaster wrote:
> > > > But what, exactly, is the question?
> > >
> > > I'm not sure after your question. The following error "iptables: target
> > > problem" comes, if i enter this rule in a user-chain:
> > > iptables -t nat -A first_group -s a.b.c.d -d x/y -p tcp --dport 10001 \
> > > -j DNAT --to-destination 1.2.3.4:25
>
> DNAT target can only be used with PREROUTING and OUTPUT.
>
> Dan
Thankfully, that is not true! I just about had a heart attack because we
make heavy use of DNAT outside of PREROUTING and OUTPUT in the automatic
NAT configuration facility of the ISCS project
(http://iscs.sourceforge.net). I've just tested it and, indeed, DNAT
can be used in user created chains as long as those chains are in the
nat table. Of course, if Postmaster's first_group chain is not in the
nat table, that would be a problem :-) - John
--
Open Source Development Corporation
Financially sustainable open source development
http://www.opensourcedevelopmentcorp.com
next prev parent reply other threads:[~2004-06-19 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 17:57 question about -t nat 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 [this message]
2004-06-19 23:25 ` Postmaster
-- strict thread matches above, loose matches on Subject: below --
2004-06-19 23:53 Jan Brand (Postmaster)
2004-06-19 16:46 Postmaster
2004-06-19 17:18 ` John A. Sullivan III
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=1087687267.2062.10.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=daniel-wittenberg@starken.com \
--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