From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: ratheesh k <ratheesh.ksz@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: NAT table bypass for local traffic
Date: Sat, 01 May 2010 16:29:25 +0200 [thread overview]
Message-ID: <4BDC3AC5.1030500@plouf.fr.eu.org> (raw)
In-Reply-To: <q2xcfeab66d1004282325wbf9a93aduf3a8fc2d82ee90b0@mail.gmail.com>
Hello,
ratheesh k a écrit :
>
> Does echo reply will show up in nat PREROUTING chain ?
No.
If conntrack saw the echo request and the related "connection" exists,
then the echo reply is in the ESTABLISHED state and by-passes the nat
chains.
If conntrack did not see the echo request or the related "connection"
was further deleted or expired, then the echo reply is in the INVALID
state and by-passes the nat chains too.
prev parent reply other threads:[~2010-05-01 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 17:19 NAT table bypass for local traffic Bill Prochazka
2010-04-28 17:59 ` Steve Fink
2010-04-28 19:46 ` Jan Engelhardt
2010-04-28 20:50 ` Bill Prochazka
2010-04-28 20:55 ` Sven-Haegar Koch
2010-04-29 6:25 ` ratheesh k
[not found] ` <001636c5c15232dea504855f65c2@google.com>
2010-04-30 6:25 ` ratheesh k
2010-04-30 7:22 ` ratheesh k
2010-05-01 4:23 ` ratheesh k
2010-05-01 14:29 ` Pascal Hambourg [this message]
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=4BDC3AC5.1030500@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=netfilter@vger.kernel.org \
--cc=ratheesh.ksz@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).