From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: Curby <curby@cur.by>
Cc: netfilter@vger.kernel.org
Subject: Re: chain/table traversal for loopback packets
Date: Thu, 13 May 2010 21:52:35 +0200 [thread overview]
Message-ID: <4BEC5883.6000309@plouf.fr.eu.org> (raw)
In-Reply-To: <AANLkTikgvzyLOesxU5RNb3MmEPPMsnotOj-oZcWGlkuT@mail.gmail.com>
Hello,
Curby a écrit :
> Hello, I'm trying to understand
> http://www.frozentux.net/iptables-tutorial/images/tables_traverse.jpg
>
> Would a packet created locally and sent over the loopback interface
> traverse the POSTROUTING and PREROUTING hooks as implied by the
> diagram,
Yes. However be aware that the nat/PREROUTING chain is skipped even for
the first packet of a new connection because at that stage the
connection is already confirmed. Thus destination NAT must be performed
in OUTPUT.
> or does the last Routing Decision notice that it's bound for
> the local host and send it straight to the beginning of the INPUT
> hook?
No.
next prev parent reply other threads:[~2010-05-13 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 18:19 chain/table traversal for loopback packets Curby
2010-05-13 19:52 ` Pascal Hambourg [this message]
2010-05-13 19:53 ` Jan Engelhardt
2010-05-13 20:00 ` Curby
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=4BEC5883.6000309@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=curby@cur.by \
--cc=netfilter@vger.kernel.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