From: Julian Gomez <kluivert@tm.net.my>
To: netfilter@lists.netfilter.org
Subject: Re: Linux firewall hardware specs
Date: Fri, 5 Sep 2003 21:02:54 +0800 [thread overview]
Message-ID: <20030905130254.GA2790@propaganda.localdomain> (raw)
In-Reply-To: <20030905121050.88228.qmail@web11605.mail.yahoo.com>
On Fri, Sep 05, 2003 at 05:10:50AM -0700, Grant Moby spoke thusly:
>I need to setup a NetFilter/Linux firewall at my company, but I'm not sure
>what spec hardware box I need.
>
>There are about 100 users surfing the web, sending and receiving email
>over a 256k line, a couple of subnets, a DMZ, etc.
OK. 256k line will be easily handled by a 486/Pentium 100Mhz host. How many
subnets and what is their interconnectivity ? Very high traffic Mbits/s ?
How many connections per second are initiated (to keep up with conntrack) ?
Short / long lived ?
The only way to be sure is to benchmark it in your own network, that said
-- I'll be surprised is a PII 266Mhz, 128Mb of RAM won't be able to handle
your setup. Unless you've got funky going-ons in your network :-)
(snip remaining)
prev parent reply other threads:[~2003-09-05 13:02 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
2003-09-05 13:02 ` Julian Gomez [this message]
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=20030905130254.GA2790@propaganda.localdomain \
--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