From: Aseem Rastogi <aseem@india.tejasnetworks.com>
To: Aseem Rastogi <aseem@india.tejasnetworks.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: NAT tables and FILTER tables
Date: Wed, 14 Sep 2005 16:57:34 +0530 [thread overview]
Message-ID: <43280926.5090508@india.tejasnetworks.com> (raw)
In-Reply-To: 43280467.4050801@india.tejasnetworks.com
in continuation:
i am actually trying to understand how nat and default filter table work
together. my understanding is this:
when a packet is encountered it is either:
1. a new connection creation request packet.
2. a packet associated with a connection that has been mangled by NAT
earlier.
3. a packet assiciated with a connection that has not been mangled by
NAT earlier.
Each case goes like this:
Case 1: NAT table is considerd. Packet passes through PREROUTING chain,
routing decision and then POSTROUTING chain.
Case 1a -- If either of them modified the packet, this packet and all
subsequent packets of this connection DO NOT PASS THROUGH FILTER TABLE
CHAINS.
Case 1b -- None of NAT tables modifies packet. It passes through FILTER
table chains as usual.
Case 2: This packet follows the fate of its earlier packets. (PREROUTING
AND POSTROUTING NAT table chains BUT NO FILTER table chains)
Case 3. Passes through FILTER TABLE chains.
is this correct??
Aseem Rastogi wrote:
> Hi,
>
> I have a small query.
>
> I have read that whenever a packet requesting a connection is
> encountered, NAT table is used. My question is : Does it mean that for
> new connection request packets ONLY NAT table is considered and not
> default FILTER table?
>
> Thanks in advance.
>
> Regards,
> Aseem.
>
--
The end is always good. If it's not good, it's not the end.
next prev parent reply other threads:[~2005-09-14 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 11:07 NAT tables and FILTER tables Aseem Rastogi
2005-09-14 11:27 ` Aseem Rastogi [this message]
2005-09-14 12:03 ` Jörg Harmuth
2005-09-14 12:21 ` Aseem Rastogi
2005-09-14 11:35 ` Rob Sterenborg
2005-09-14 13:13 ` /dev/rob0
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=43280926.5090508@india.tejasnetworks.com \
--to=aseem@india.tejasnetworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox