From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Alaadin <alaadin@alaadin.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: how many rules can be added?
Date: Thu, 16 Sep 2004 12:49:35 -0400 [thread overview]
Message-ID: <1095353375.2064.143.camel@localhost> (raw)
In-Reply-To: <1314.81.10.7.66.1095343827.squirrel@81.10.7.66>
On Thu, 2004-09-16 at 10:10, Alaadin wrote:
> Hello,
>
> how many ip tables rules can i add ?
> i added already 40
> if i added untill 100 or 500 rule
> would this make problems ?
> would this make the system lag ?
> would this make the system hang
> how many ip tables rules can i add ? or its unlimited?
You can add many more than 500! For the complex security we manage on
the ISCS project (http://iscs.sourceforge.net), we frequently encounter
rule sets many times this size.
As your rule set grows, you will want to pay attention to two particular
needs:
1) Optimize the traversal of your rule sets by using user defined
chains. This is analogous to database indexing. Sort your packets as
they come in and direct them to a subset of the total rules.
2) Optimize the load time of the rules. This is noticeable even with
relatively small rule sets. Use iptables-restore -n instead of loading
each rule separately with an iptables command.
Hope this helps - John
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
next prev parent reply other threads:[~2004-09-16 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 14:10 how many rules can be added? Alaadin
2004-09-16 16:48 ` Marc Haber
2004-09-16 16:49 ` John A. Sullivan III [this message]
2004-09-16 21:26 ` Frank Gruellich
2004-09-17 9:33 ` Jan Du Caju
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=1095353375.2064.143.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=alaadin@alaadin.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