From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Problem behind my DMZ
Date: Thu, 8 Jan 2004 17:22:59 +0000 [thread overview]
Message-ID: <200401081722.59297.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <Law11-F6JcZikaTAbNF00019dce@hotmail.com>
On Thursday 08 January 2004 5:12 pm, Martin Leduc wrote:
> Good morning Mr Stone,
>
> I'm sorry, I guess I dont explain correctly.
>
> I have a IP range about /28 Public IP. I have 2 NIC in my Linux BOX, one
> for the Internet and the other for my servers Switch.
Oh. If you do not have a DMZ network then the suggestion made earlier to
subnet your /28 will not work. We thought you had a genuinely separate DMZ
with the publicly-accessible servers on it.
> My Topology:
>
> 192.168.0.2 (WEB) <---|
> 192.168.0.3 (DNS) <---|
> 192.168.0.4 (MAIL)<---|
> eth1
> 192.168.0.1 (GW)
> -------
> | BOX |
> -------
> ^
> eth0 : 20.0.0.1
> eth0:0 : 20.0.0.2 (DNAT 192.168.0.2)
> eth0:1 : 20.0.0.3 (DNAT 192.168.0.3)
> eth0:2 : 20.0.0.4 (DNAT 192.168.0.4)
> ^
> INTERNET
So where are the local client machines?
> So I have rules
> iptables -t nat -A PREROUTING -p tcp/udp --port X -s 20.0.0.2 \
> -j DNAT --to-destination 192.168.0.2:X
>
> And my postrouting
>
> iptables -t nat -A POSTROUTING -o eth0 -s 192.168.0.2 -j SNAT --to-source
> 20.0.0.2
I still don't understand where the local client machines are on your network.
What you have described above should work fine for clients which are out on
the Internet.
> My FORWARD rules are WideOpen
UGH!
> Spliting my DNS is not an option.
Why not?
Regards,
Antony.
--
Normal people think "If it ain't broke, don't fix it".
Engineers think "If it ain't broke, it doesn't have enough features yet".
next prev parent reply other threads:[~2004-01-08 17:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 17:12 Problem behind my DMZ Martin Leduc
2004-01-08 17:22 ` Antony Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 12:08 Martin Leduc
2004-01-10 13:26 Martin Leduc
2004-01-10 12:55 Martin Leduc
2004-01-09 9:54 Martin Leduc
2004-01-09 10:57 ` Antony Stone
2004-01-09 15:26 ` Ramin Dousti
2004-01-09 2:19 Martin Leduc
2004-01-09 4:14 ` Ramin Dousti
2004-01-08 17:46 Martin Leduc
2004-01-08 17:53 ` Antony Stone
2004-01-08 15:53 Martin Leduc
2004-01-08 16:16 ` Antony Stone
2004-01-08 18:10 ` Ramin Dousti
2004-01-08 17:17 ` Antony Stone
2004-01-08 19:18 ` Ramin Dousti
2004-01-08 0:19 Martin Leduc
2004-01-08 2:27 ` Chris Brenton
2004-01-08 16:31 ` Michael Gale
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=200401081722.59297.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