From: "Lluís Batlle" <viriketo@gmail.com>
To: lartc@mailman.ds9a.nl, netfilter@lists.netfilter.org
Subject: More on conntrack + NAT + mangle/nat tables
Date: Wed, 6 Jul 2005 11:17:49 +0200 [thread overview]
Message-ID: <45219fb00507060217450a89ee@mail.gmail.com> (raw)
I already understood that a packet enters chains in the 'nat' table
only if it is the _first_ packet of a connection. In that case, we may
do SNAT in the POSTROUTING chain of the 'nat' table.
So, the packets arrive to the POSTROUTING chain of the 'mangle' table
with the source IP address changed (if it's said by the rules of the
'nat' table).
BUT, for the rest of the packets (not the first ones) of a connection,
packets enter the POSTROUTING chain of the 'mangle' table _without_ a
changed source IP address. Is this the expected behaviour of
netfilter/conntrack?
To me, it's quite strange.
- I'm learning about the whole netfilter/policy router these days :)
So I write a lot about that, which sounds strange to me. I hope I'm
not annoying to the list.
Thanks a lot.
- Lluís
next reply other threads:[~2005-07-06 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 9:17 Lluís Batlle [this message]
2005-07-06 10:09 ` More on conntrack + NAT + mangle/nat tables Jörg Harmuth
2005-07-06 10:20 ` Lluís Batlle
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=45219fb00507060217450a89ee@mail.gmail.com \
--to=viriketo@gmail.com \
--cc=lartc@mailman.ds9a.nl \
--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