From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: DMZ to DMT through ROUTER problem !
Date: Thu, 20 May 2004 18:34:23 +0100 [thread overview]
Message-ID: <200405201834.23351.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <200405201832.26844.liste@zerozone.it>
On Thursday 20 May 2004 5:32 pm, O-Zone wrote:
> On Thursday 20 May 2004 18:07, Antony Stone wrote:
> > What about the rest of rc.firewall? You have posted your POSTROUTING
> > SNAT rules - do you have any PREROUTING DNAT rules to convert 151.8.47.B
> > into 192.168.0.3?
>
> Yes ! Here is (for SIENA only):
>
> $IPTABLES -t nat -A PREROUTING -p TCP -i $INET_IFACE -d $SIENA_IP -m
> multiport - --dports 25,53,80,110 -j DNAT --to-destinati$
> $IPTABLES -t nat -A PREROUTING -p UDP -i $INET_IFACE -d $SIENA_IP -m
> multiport - --dports 53 -j DNAT --to-destination $DMZ_SI$
Your PREROUTING DNAT rules specify the input interface (-i $INET_IFACE),
therefore they do not apply to packets arriving on any other interface.
Change this, either by removing the -i option altogether, or by adding extra
rules to apply to the other interrface/s on your firewall from which you want
to allow packets to be DNATted, and things should work.
Regards,
Antony.
--
If the human brain were so simple that we could understand it,
we'd be so simple that we couldn't.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-05-20 17:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 11:18 DMZ to DMT through ROUTER problem ! O-Zone
2004-05-20 12:30 ` Antony Stone
2004-05-20 12:54 ` O-Zone
2004-05-20 13:22 ` Antony Stone
2004-05-20 14:37 ` O-Zone
2004-05-20 14:45 ` Antony Stone
2004-05-20 14:58 ` O-Zone
2004-05-20 15:07 ` Antony Stone
2004-05-20 15:53 ` O-Zone
2004-05-20 16:07 ` Antony Stone
2004-05-20 16:32 ` O-Zone
2004-05-20 17:34 ` Antony Stone [this message]
2004-05-20 17:44 ` Antony Stone
2004-05-21 9:30 ` O-Zone
2004-05-21 10:19 ` Antony Stone
2004-05-21 14:08 ` O-Zone
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=200405201834.23351.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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