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 15:45:32 +0100 [thread overview]
Message-ID: <200405201545.32872.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <200405201637.54395.liste@zerozone.it>
On Thursday 20 May 2004 3:37 pm, O-Zone wrote:
> On Thursday 20 May 2004 15:22, Antony Stone wrote:
> > You need to make sure that the reply packets go back through the
> > firewall, as well as the forward packets. The easiest way to do this is
> > by adding a SNAT rule so that as far as the destination server is
> > concerned, the packets came from the firewall, not the real client, and
> > therefore the server sends the replies back to the firewall (which then
> > reverse-NATs them and returns the replies to the original client
> > machine).
> >
> > Therefore in your case something such as:
> >
> > iptables -A POSTROUTING -t nat -s 192.168.0.0/24 -d 192.168.0.0/24 -j
> > SNAT --to 192.168.0.1
>
> But, i think, i need to add other rules because the original connection
> came from 192.168.0.x to 151.8.47.x, right ?
Yes, but that destination address has already been changed by your PREROUTING
rule, and is now 192.168.0.0/24 - that's the whole point. If the
destination address had not been changed (ie: if the client had contacted the
server's real IP address instead of a pretend one), you wouldn't need to
change the source address as well.
If you think you need other rules, please explain what they would be and why
they are needed - it's entirely possible I have missed something about your
setup.
Regards,
Antony.
--
The truth is rarely pure, and never simple.
- Oscar Wilde
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-05-20 14:45 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 [this message]
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
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=200405201545.32872.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