All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Harmuth" <harmuth@mnemon.de>
To: netfilter@lists.netfilter.org
Subject: Re: More on conntrack + NAT + mangle/nat tables
Date: Wed, 06 Jul 2005 12:09:22 +0200	[thread overview]
Message-ID: <42CBADD2.8040106@mnemon.de> (raw)
In-Reply-To: <45219fb00507060217450a89ee@mail.gmail.com>

Lluís Batlle schrieb:
> 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).

No. According to the picture found at

http://iptables-tutorial.frozentux.net/chunkyhtml/traversingoftables.html

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.

> - 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.

I can only speak for myself - no, you aren't :)

Have a nice time,

Joerg



  reply	other threads:[~2005-07-06 10:09 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 [this message]
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=42CBADD2.8040106@mnemon.de \
    --to=harmuth@mnemon.de \
    --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.