From: Amin Azez <azez@ufomechanic.net>
To: netfilter-devel@lists.netfilter.org
Subject: return flow NAT table on POSTROUTING
Date: Mon, 15 May 2006 15:50:53 +0100 [thread overview]
Message-ID: <e4a4gh$7jk$1@sea.gmane.org> (raw)
I've observed on kernel 2.6.11.7 that return flows for SNAT'd
connections do not pass through the NAT chain in the POSTROUTING table.
They do however pass through the MANGLE chain in the POSTROUTING table.
Is this to be expected?
(Of course the original flow did pass through the NAT chain which is how
the SNAT occurred).
Sam
next reply other threads:[~2006-05-15 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 14:50 Amin Azez [this message]
2006-05-15 18:44 ` return flow NAT table on POSTROUTING Patrick McHardy
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='e4a4gh$7jk$1@sea.gmane.org' \
--to=azez@ufomechanic.net \
--cc=netfilter-devel@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.