From: Matt Zagrabelny <mzagrabe@d.umn.edu>
To: elhadad@cisco.com
Cc: netfilter@vger.kernel.org
Subject: Re: iptables and performance
Date: Tue, 13 May 2008 10:29:48 -0500 [thread overview]
Message-ID: <1210692588.545.119.camel@grateful.d.umn.edu> (raw)
In-Reply-To: <1210661965.5829.227.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
On Tue, 2008-05-13 at 09:59 +0300, Eli Hadad wrote:
> Hi all,
>
> I am new to iptables and have few question I hope you can help with:
> 1. Is there a limit to the number of rules I can add to specific chain?
> I need to have around 20000 rules.
> 2. What is the performance implications of using this large number of
> rules? Is there any numbers people can share.
> 3. I also saw the HIPAC project which claim to have much better
> performance. Is there any work done to integrate same type of
> functionality into iptables?
Google: hipac ipset
Look at the first pdf link. It talks about performance and netfilter. It
also addresses HIPAC and ipset.
I would say that you want to look at ipset.
Cheers,
--
Matt Zagrabelny - mzagrabe@d.umn.edu - (218) 726 8844
University of Minnesota Duluth
Information Technology Systems & Services
PGP key 1024D/84E22DA2 2005-11-07
Fingerprint: 78F9 18B3 EF58 56F5 FC85 C5CA 53E7 887F 84E2 2DA2
He is not a fool who gives up what he cannot keep to gain what he cannot
lose.
-Jim Elliot
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-13 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1210661080.5829.225.camel@localhost.localdomain>
2008-05-13 6:59 ` iptables and performance Eli Hadad
2008-05-13 15:29 ` Matt Zagrabelny [this message]
2008-05-13 20:03 ` Eli Hadad
2008-05-13 16:24 ` Grant Taylor
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=1210692588.545.119.camel@grateful.d.umn.edu \
--to=mzagrabe@d.umn.edu \
--cc=elhadad@cisco.com \
--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