Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Eli Hadad <elhadad@cisco.com>
To: netfilter@vger.kernel.org
Subject: iptables and performance
Date: Tue, 13 May 2008 09:59:25 +0300	[thread overview]
Message-ID: <1210661965.5829.227.camel@localhost.localdomain> (raw)
In-Reply-To: <1210661080.5829.225.camel@localhost.localdomain>


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?

Thanks in advance,
Eli


       reply	other threads:[~2008-05-13  6:59 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 ` Eli Hadad [this message]
2008-05-13 15:29   ` iptables and performance Matt Zagrabelny
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=1210661965.5829.227.camel@localhost.localdomain \
    --to=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