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: Mon, 14 Jan 2008 10:53:14 +0100 [thread overview]
Message-ID: <478B310A.3040300@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0801140944000.10906@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Jan 14 2008 07:04, Patrick McHardy wrote:
>> Jan Engelhardt wrote:
>>> the following series implements xt_RAWNAT, a target to do network
>>> address translation not depending on conntrack. I still have an issue
>>> though, if you have an idea what could be wrong, please let me know.
>> Whats the advantage over using the TC NAT action?
>
> Let me put it this way... “what is tc?”
>
> - tc is a real black-box to most users;
> lack of documentation (despite lartc.org efforts)
That should be fixed by writing documentation, not code :)
> - act_nat only works like NETMAP, i.e.
> on outgoing packets, you can only change the source addr
I guess it could be changed to support DNAT on outgoing packets
quite easily.
> At which point I would be asking: why is tc trying to do the same
> as netfilter mangling targets?
Well, true, it would be nice to be able to do this within
netfilter without TC actions. 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.
Another issue is IPv6 support. Everyone agrees that we don't
want to support IPv6 NAT. So this would have to be removed.
-
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-01-14 9:58 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 [this message]
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
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=478B310A.3040300@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).