Linux Netfilter discussions
 help / color / mirror / Atom feed
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 13:30:31 +0100	[thread overview]
Message-ID: <200405201330.31625.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <200405201318.34706.liste@zerozone.it>

On Thursday 20 May 2004 12:18 pm, O-Zone wrote:

> i've a big problem. Here's a little diagram:
>
> [INTRANET 10.0.0.0/24]-------------+
>                                                       +--[ROUTER]--(NET)
> [DMZ SERVER A - 192.168.0.2]----+
> [DMZ SERVER B - 192.168.0.3]----+
>
> Each DMZ server is mapped to it's PUBLIC IP. For example:
>
> 151.8.47.A ----> 192.168.0.2
> 151.8.47.B ----> 192.168.0.3
>
> and all work perfectly !!!
>
> The problem is when, from 192.168.0.2, i try to connect to 151.08.47.B
> (trat's mapped to 192.168.0.3): packets die on ROUTER.

It's the reply packets which are the problem.

Think about a TCP connection:

1. SYN packet from 192.168.0.2 to 151.8.47.B goes to the firewall.
2. Firewall DNATs 151.8.47.B to 192.168.0.3
3. SYN packet goes from firewall to 192.168.0.3
4. 192.168.0.3 sends SYN-ACK to 192.168.0.2 on local net (not via firewall)
5. 192.168.0.2 wonders why it got a SYN-ACK from 192.168.0.3 when it sent the 
SYN to 151.8.47.B

http://www.netfilter.org/documentation/HOWTO/NAT-HOWTO-10.html

Regards,

Antony.

-- 
"The problem with television is that the people must sit and keep their eyes 
glued on a screen; the average American family hasn't time for it."

 - New York Times, following a demonstration at the 1939 World's Fair.

                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-05-20 12:30 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 [this message]
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
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=200405201330.31625.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