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 17:07:30 +0100	[thread overview]
Message-ID: <200405201707.30559.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <200405201753.40647.liste@zerozone.it>

On Thursday 20 May 2004 4:53 pm, O-Zone wrote:

> On Thursday 20 May 2004 17:07, Antony Stone wrote:
> > If you do not in fact already have the PREROUTING DNAT rules, then what
> > do you mean by "Each DMZ server is mapped to its PUBLIC IP"?   Maybe I
> > misunderstood what you have already done, and already have working, and
> > what problem is still left to solve?
>
> Here's the problem (TCPDUMP on 192.168.0.1):
> root@bastion:/etc/rc.d# tcpdump -i eth2 dst 151.8.47.B
> 17:45:52.507152 IP 192.168.0.2.45621 > 151.8.47.B.pop3: S
> 1931786477:1931786477(0) win 5840 <mss 1460,sackOK,timestamp
>
> but on 151.8.47.B (192.168.0.3) no any packet arrive. This is a piece of
> rc.firewall:

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?

If you do not have any PREROUTING rules, I remain confused about how this was 
already working from the Internet as you said previously, but try:

iptables -A PREROUTING -t nat -p tcp --dport 110 -d 151.8.47.B -j DNAT --to 
192.168.0.3

Regards,

Antony.

-- 
There are only 10 types of people in the world:
those who understand binary notation,
and those who don't.

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



  reply	other threads:[~2004-05-20 16:07 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 [this message]
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=200405201707.30559.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