All of lore.kernel.org
 help / color / mirror / Atom feed
From: Payal Rathod <payalrathod@gmail.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: NATting again
Date: Sat, 17 Jul 2004 09:37:22 +0530	[thread overview]
Message-ID: <f51b72bc040716210743d323c2@mail.gmail.com> (raw)
In-Reply-To: <200407161927.55940.Antony@Soft-Solutions.co.uk>

Hi,

On Fri, 16 Jul 2004 19:27:55 +0100, Antony Stone 
> > Why is the FORWARD rule needed here?
> 
> Because without it, the DNAT rule will change the destination address of the
> packets, and then they won't be allowed through the next chain in sequence
> (PREROUTING --> FORWARD --> POSTROUTING).

I am sorry I don't undertand it much. Tell me one more thing if I have
10 machines in DMZ with 10 ports each to allow for outside world, does
that mean writing 100 FORWARD rules and 100 PREROUTING rules?
 
> If you *didn't* have a DNAT rule, you would need a FORWARD rule, so I think it
> would seem strange if you didn't need a FORWARD rule just because you'd
> changed the destination address.   (For example, what would happen if you
> used a DNAT rule which "changed" the address to the same as it already was?
> Or maybe two DNAT rules in a row - one changes it, and the next changes it
> back again?)

Sorry again, but this is just sounding greek to me now :)

With warm regards,
-Payal


  reply	other threads:[~2004-07-17  4:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16 15:50 NATting again Payal Rathod
2004-07-16 16:03 ` Antony Stone
2004-07-16 17:49   ` Payal Rathod
2004-07-16 18:27     ` Antony Stone
2004-07-17  4:07       ` Payal Rathod [this message]
2004-07-17  9:08         ` Antony Stone

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=f51b72bc040716210743d323c2@mail.gmail.com \
    --to=payalrathod@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.