From: Marek Kierdelewicz <marek@koba.pl>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Fwd: iptables-1.4.1-1.4.2 change "Warn about use of DROP in nat table" (fwd)
Date: Tue, 13 Jan 2009 13:22:30 +0100 [thread overview]
Message-ID: <20090113132230.3aa55c40@catlap> (raw)
In-Reply-To: <alpine.LSU.2.00.0901131030410.7823@fbirervta.pbzchgretzou.qr>
Hello,
>If you are _that_ concerned about CPU usage (and I remember there
>being an analysis of Netfilter's speed compared to other solutions; a
>document somewhere on people.netfilter.org), you would have done it
>in the mangle table, not in nat, short of saying that that is
>probably not the purpose of mangle either.
>There were once thoughts to combine some tables because of the
>redundancy, but the thought timed out :)
Thanks for informative and prompt response Jan.
Regards,
--
Marek Kierdelewicz
Kierownik Działu Systemów Sieciowych, KoBa
Manager of Network Systems Department, KoBa
tel. (85) 7406466; fax. (85) 7406467
e-mail: admin@koba.pl
--
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
parent reply other threads:[~2009-01-13 12:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.LSU.2.00.0901131030410.7823@fbirervta.pbzchgretzou.qr>]
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=20090113132230.3aa55c40@catlap \
--to=marek@koba.pl \
--cc=jengelh@medozas.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).