From: "Lluís Batlle" <viriketo@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: More on conntrack + NAT + mangle/nat tables
Date: Wed, 6 Jul 2005 12:20:49 +0200 [thread overview]
Message-ID: <45219fb0050706032038dca0e8@mail.gmail.com> (raw)
In-Reply-To: <42CBADD2.8040106@mnemon.de>
Oh, my fault. :) I mislooked at the diagram :) Everything is fine, so,
about nat + mangle tables.
So, I think conntrack NAT happens after the mangle POSTROUTING chain.
So, after routing.
Thanks :)
On 7/6/05, Jörg Harmuth <harmuth@mnemon.de> wrote:
> packet flow is:
>
> ... --> [mangle:POSTROUTING] --> [nat:POSTROUTING]
>
> So, all packets arrive in mangle:POSTROUTING with their source address
> unchanged. DNAT - if configured - is already applied to the packet.
>
> If I'm telling old stories now, forget it, but you can modify this
> script to fit your needs:
>
> http://iptables-tutorial.frozentux.net/scripts/rc.test-iptables.txt
>
> Following the log (and /proc/net/ip_conntrack) you see the packet flow
> in detail. And you see when [S|D]NAT ist applied.
prev parent reply other threads:[~2005-07-06 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 9:17 [LARTC] More on conntrack + NAT + mangle/nat tables Lluís Batlle
2005-07-06 9:17 ` Lluís Batlle
2005-07-06 10:09 ` Jörg Harmuth
2005-07-06 10:20 ` Lluís Batlle [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=45219fb0050706032038dca0e8@mail.gmail.com \
--to=viriketo@gmail.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 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.