From: Feizhou <feizhou@linuxmail.org>
To: netfilter@lists.netfilter.org
Subject: Re: NAT performance
Date: Fri, 13 May 2005 19:52:31 +0800 [thread overview]
Message-ID: <428494FF.9020707@linuxmail.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0505131038510.2119@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> On Fri, 13 May 2005, Christophe SUIRE wrote:
>
>
>>This not a problem with the network card, because when i do the test
>>with only firewall routing i have a total bandwidth used near to
>>500Mbit/s.
>>But when i add an SNAT translation for each network (10) the total
>>bandwidth used is near 170Mbit/s.
>>So why this important difference without an with NAT ??
>
>
> NAT *is* expensive. Have a look at the paper on netfilter performance
> tests and comparisons at http://people.netfilter.org/kadlec/nftest.pdf
the ip_conntrack module sucks. Lovely cpu chewer.
prev parent reply other threads:[~2005-05-13 11:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 21:24 NAT performance Christophe SUIRE
2005-05-13 0:03 ` Taylor, Grant
2005-05-13 7:16 ` Christophe SUIRE
[not found] ` <Pine.LNX.4.60.0505130423320.5558@darkstar.sysinfo.com>
2005-05-13 8:33 ` Christophe SUIRE
2005-05-13 9:22 ` Jozsef Kadlecsik
2005-05-13 9:51 ` Christophe SUIRE
2005-05-13 9:57 ` Jozsef Kadlecsik
2005-05-13 10:14 ` Jozsef Kadlecsik
2005-05-13 10:19 ` Christophe SUIRE
2005-05-13 10:18 ` Christophe SUIRE
2005-05-13 11:52 ` Feizhou [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=428494FF.9020707@linuxmail.org \
--to=feizhou@linuxmail.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox