From: Gavin Hamill <gdh@acentral.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Linux firewall hardware specs
Date: Fri, 5 Sep 2003 13:55:15 +0100 [thread overview]
Message-ID: <200309051355.15499.gdh@acentral.co.uk> (raw)
In-Reply-To: <20030905121050.88228.qmail@web11605.mail.yahoo.com>
On Friday 05 September 2003 13:10, Grant Moby wrote:
> There are about 100 users surfing the web, sending and
> receiving email over a 256k line, a couple of subnets,
> a DMZ, etc.
Okies, we're running a fully stateful netfilter firewall on an old P233 with a
2Mbps leased line, 10 very busy servers, another 50 desktop machines, and the
loadaverage is typically about 0.01.
With 'fprobe' running for more accurate 'NetFlow' traffic reporting, the
loadavg rises to 0.10, typically.
Even adding snort to the equation, the load settles at only 0.60 :)
I don't know how much extra load would be added by using cheap network cards,
but we have a pair of Intel 10/100s in the firewall, and the box has been
running flawlessly for months...
Cheers,
Gavin.
next prev parent reply other threads:[~2003-09-05 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 12:10 Linux firewall hardware specs Grant Moby
2003-09-05 12:39 ` Aldo S. Lagana
2003-09-05 12:55 ` Gavin Hamill [this message]
2003-09-05 13:02 ` Julian Gomez
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=200309051355.15499.gdh@acentral.co.uk \
--to=gdh@acentral.co.uk \
--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.