All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rinse Kloek" <rinse@solcon.nl>
To: netfilter@lists.netfilter.org
Subject: Iptables efficiency
Date: Mon, 10 Mar 2003 19:04:15 +0100	[thread overview]
Message-ID: <007b01c2e72f$76712180$0200a8c0@rinse> (raw)

We use a RedHat 7.3 machine as bridge on a P3 1.8 Ghz with 2 64 bits
Gigabit interfaces. On the machine we have a lot of iptables rules like :
            all  --  213.134.x.0        0.0.0.0/0
            all  --  0.0.0.0/0            213.134.x.0
TOS    all  --  213.134.x.4        0.0.0.0/0          TOS set 0x08
            all  --  0.0.0.0/0            213.134.x.4

We have about 3200 iptables rules on our bridge. I've tested today to
remove 1000 of these rules. The load dropped from about 40% to 25%. So I
think the iptables rule take up the most of the CPU load. Do you think this
is a problem of ineffeciency of iptables or just a 'limitation' in the
TCP/IP stack of linux ?

regards Rinse



             reply	other threads:[~2003-03-10 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 18:04 Rinse Kloek [this message]
2003-03-11 13:13 ` Iptables efficiency Raymond Leach
2003-03-11 14:31 ` Joel Newkirk

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='007b01c2e72f$76712180$0200a8c0@rinse' \
    --to=rinse@solcon.nl \
    --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.