All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn <core@enodev.com>
To: Augusto Flavio <augustoflavioms@yahoo.com.br>
Cc: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: Re: iptables support this?
Date: 18 Jul 2003 10:10:48 -0500	[thread overview]
Message-ID: <1058541048.2196.8.camel@localhost> (raw)
In-Reply-To: <20030718145526.49893.qmail@web41505.mail.yahoo.com>

Performance no fail much, but you fail to mention how it is all
organized. Not that it should matter much with modern CPUs. How many
sequential steps in the path you're worried about? 500? That would be
just silly.

I'm guessing you have different rules for different IP or IP range
matches. No big deal.

Keep in mind if you're that worried about speed, maybe you ought to
think about making your routing and firewalling separate.


On Fri, 2003-07-18 at 09:55, Augusto Flavio wrote:
> Hi,
> The IPTables support some like 500 rules? 
> The performance fail much?
> 
> 
> Tkz!



  reply	other threads:[~2003-07-18 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 14:55 iptables support this? Augusto Flavio
2003-07-18 15:10 ` Shawn [this message]
2003-07-19  4:08 ` George Vieira

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=1058541048.2196.8.camel@localhost \
    --to=core@enodev.com \
    --cc=augustoflavioms@yahoo.com.br \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.