From: "P.Italiaander" <pc-secure@home.nl>
To: netfilter@lists.netfilter.org
Subject: Re: Performance Decrease
Date: Mon, 12 May 2003 01:36:48 +0200 [thread overview]
Message-ID: <200305120136.48436.pc-secure@home.nl> (raw)
In-Reply-To: <001201c31411$b3ccaa40$c90c010a@TMCSHAWN>
Op dinsdag 6 mei 2003 22:54, schreef Shawn Mall:
> I am running iptables version 1.2.2 -- This has never been an issue until I
> have begun to do some bandwidth intensive stuff. I also had a friend of
> mine point this out as well...
>
> There seems to be a huge performance decrease when using iptables. I am not
> sure where the bottleneck is occuring. My friend has a 3Mbit/sec pipe, was
> getting about 500kb/sec on average, and since implenting iptables, is only
> receiving about 50kb/sec. That is a huge decrease. Can anybody point out
> what is going wrong?
>
> Thanks,
> Shawn
need more info on rule-set for this.
Perhaps a faulty rule with an 'limit' and high burst max, so instead that
limiting from outside (like Pings of Death) , you limit your own connection.
Pascal
next prev parent reply other threads:[~2003-05-11 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 20:54 Performance Decrease Shawn Mall
2003-05-11 23:36 ` P.Italiaander [this message]
2003-05-12 4:49 ` Dharmendra.T
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=200305120136.48436.pc-secure@home.nl \
--to=pc-secure@home.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox