From: Julian Gomez <kluivert@tm.net.my>
To: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: Performance losings with iptables
Date: Tue, 20 May 2003 18:09:26 +0800 [thread overview]
Message-ID: <20030520100926.GA1209@floyd> (raw)
In-Reply-To: <1053417001.1964.86.camel@kermit.spenneberg.de>
On Tue, May 20, 2003 at 09:50:01AM +0200, Ralf Spenneberg spoke thusly:
>Am Die, 2003-05-13 um 17.40 schrieb Michael Albrecht:
>> iptables -A input -s 192.168.81.xxx
>> i will lose a lot of perfomance (for
>> example: apache take a lot of time, ssh ...) Wenn i show the perfomance
>> with vmstat - vmstat says that 99 % is
As Michael has already mentioned, I too doubt its an iptables fault. I've
had in excess of 1,300 rules running on a production firewall, for dynamic
dumping of Nimda infected hosts. Its almost certainly a name resolving
issue as Michael has already pointed to.
next prev parent reply other threads:[~2003-05-20 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 15:40 Performance losings with iptables Michael Albrecht
2003-05-20 7:50 ` Ralf Spenneberg
2003-05-20 10:09 ` Julian Gomez [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 15:57 Michael Albrecht
2003-05-13 16:48 ` Aldo Lagana
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=20030520100926.GA1209@floyd \
--to=kluivert@tm.net.my \
--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