From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: xt_RAWNAT target idea
Date: Tue, 15 Jan 2008 07:34:45 +0100 [thread overview]
Message-ID: <478C5405.6040104@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0801141618030.10906@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Jan 14 2008 10:53, Patrick McHardy wrote:
>
>> But adding a new chain to the raw table is a high price, every new
>> netfilter hooks costs quite a bit of performance. Why not simply do
>> this in the mangle table? That will also make rerouting in OUTPUT
>> work as a side effect.
>
> I think the issue that I tried to outrun was that if I mangle the
> address in NF_IP_PRI_MANGLE, then IP_NF_PRI_CONNTRACK_HELPER and
> IP_NF_PRI_CONNTRACK_CONFIRM gets confused because I change the
> address after NF_IP_PRI_CONNTRACK.
>
> IOW: conntrack sees the packet, I mangle it in mangle,
> and then the other conntrack hooks get confused.
> That is why I thought I need some hook after
> NF_IP_PRI_CONNTRACK_CONFIRM.
They probably put the wrong address in the hash tables. The main
use for this seems to be avoiding the use of conntrack anyways,
but to make them play nicely together I guess you'd have to
mangle the conntrack tuple in case conntrack is used.
prev parent reply other threads:[~2008-01-15 6:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 16:08 xt_RAWNAT target idea Jan Engelhardt
2008-01-13 16:09 ` [xt_RAWNAT 1/3] Make room in the hook priority list Jan Engelhardt
2008-01-13 16:10 ` [xt_RAWNAT 2/3] Extend iptable_raw by POSTROUTING hook Jan Engelhardt
2008-01-13 16:10 ` [xt_RAWNAT 3/3] xt_RAWNAT code Jan Engelhardt
2008-01-13 16:25 ` Jan Engelhardt
2008-01-13 16:22 ` [xt_RAWNAT] iptables libxt_RAWNAT Jan Engelhardt
2008-01-14 6:04 ` xt_RAWNAT target idea Patrick McHardy
2008-01-14 9:45 ` Jan Engelhardt
2008-01-14 9:53 ` Patrick McHardy
2008-01-14 14:28 ` Jan Engelhardt
2008-01-14 14:39 ` Jozsef Kadlecsik
2008-01-14 22:43 ` Amos Jeffries
2008-01-14 15:20 ` Jan Engelhardt
2008-01-15 6:34 ` Patrick McHardy [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=478C5405.6040104@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).