From: Jason Joines <joines@bus.okstate.edu>
To: netfilter@lists.netfilter.org
Subject: Another Hardware Sizing Question
Date: Fri, 05 Sep 2003 11:26:28 -0500 [thread overview]
Message-ID: <3F58B934.3060902@bus.okstate.edu> (raw)
We have a subnet with a potential of 1022 hosts. Each machine is
connected to a 100 Mbps switch. The connection from our subnet to the
main university network is I believe OC-3, ~154 Mbps. There are
currently less than 500 active machines on the network. They do the
normal web brosing, and connect to NetWare and Domino servers outside
the subnet. With that, the maximum traffic we've ever seen between our
subnet and the rest of the world is about 40 Mbps.
We'd like to put all the boxes on our subnet behind and IPTables
firewall and NAT them. We'd also like to take into consideration the
possibility of the number of machines growing to ~1000. We have quite a
few spare PIII 450 boxes setting around.
What would be the mininum, ideal, etc., hardware setup for this
environment.
Thanks,
Jason Joines
Open Source = Open Mind
========================
next reply other threads:[~2003-09-05 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 16:26 Jason Joines [this message]
2003-09-08 5:41 ` Another Hardware Sizing Question Dharmendra.T
2003-09-08 14:34 ` Jason Joines
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=3F58B934.3060902@bus.okstate.edu \
--to=joines@bus.okstate.edu \
--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