From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: iptables-list <netfilter@lists.samba.org>
Subject: Re: Syntax/NAT OUTPUT
Date: Tue, 9 Jul 2002 21:27:03 +0100 [thread overview]
Message-ID: <20020709202705.FPXL290.mta02-svc.ntlworld.com@there> (raw)
In-Reply-To: <000801c2279c$6e2364f0$4fcf3cd0@nebuchadnezza>
On Tuesday 09 July 2002 11:59 pm, Tim wrote:
> Scenario: router eth0 to Fwall 192.168.2.2
> Fwall eth0 from router 192.168.2.1
> Fwall eth1 from DMZ 172.16.1.1
> Fwall eth2 from LAN 192.168.1.1
>
> My understanding of concepts of filtering and nat
>
> Pinging from the router eth0 thu Fwall eth2 to LAN, it first goes through
> PREROUTING nat table then the filter INPUT----this the path it takes to get
> to any box in the LAN .....yes ?
No. Packets only go through the INPUT chain if they are addressed to the
firewall itself.
If they are being routed through the firewall to something on the other side,
they go through the FORWARD chain.
You're right about them going through PREROUTING first, though, and they also
go through POSTROUTING afterwards.
> To get a reply from this ping it must go thru the NAT OUTPUT then filter
> OUTPUT.....this is my understanding of the return path for this ping from
> the router eth0.....is this correct so far ?
The OUTPUT chain is only for packets originating on the firewal itself, so
unless you type the ping command on the firewall, the OUTPUT chains
(filtering and nat) are not involved.
Antony.
next prev parent reply other threads:[~2002-07-09 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 22:59 Syntax/NAT OUTPUT Tim
2002-07-09 20:27 ` Antony Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 21:58 George Vieira
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=20020709202705.FPXL290.mta02-svc.ntlworld.com@there \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.samba.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