Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Feizhou <feizhou@linuxmail.org>
To: NetFilter List <netfilter@lists.netfilter.org>
Subject: Re: Rule Set Size vs Performance Follow-up
Date: Fri, 30 Jul 2004 00:46:31 +0800	[thread overview]
Message-ID: <410929E7.5040708@linuxmail.org> (raw)
In-Reply-To: <1091113691.9879.9.camel@dchws.tqmcube.com>

David Cary Hart wrote:
> The issue was a large number of dpt 80 rules that are added by a script
> from Snort exploits.
> 
> The suggested solution was to move these to a new chain so that only
> packets destined for httpd would have to traverse several hundred
> (hopefully temporary) rules.
> 
> Not only does this make logical sense but I notice a definite
> improvement in DNS (which is the most apparent performance issue).

You'd probably also want to make sure you don't use any connection 
tracking rules and therefore not load the conntrack module. In my case, 
dns queries took seconds (as opposed to milliseconds) to get an answer 
back from the dnscache.


      reply	other threads:[~2004-07-29 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29 15:08 Rule Set Size vs Performance Follow-up David Cary Hart
2004-07-29 16:46 ` 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=410929E7.5040708@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