All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Daniel Franklin <joshua@iocc.com>
To: lartc@vger.kernel.org
Subject: [LARTC] good hardware
Date: Wed, 05 Feb 2003 21:59:58 +0000	[thread overview]
Message-ID: <marc-lartc-104448243926562@msgid-missing> (raw)

I've searched the list archives and haven't found any information on this. 

I realize that many users are routing in a home or small office 
environment but I think there is also a place for "enterprise" 
routing. But knowing how to configure the software is only part
of a low-latency router--you also need good hardware. 

Are there any thoughts on good configurations? 
NICs: I've seen several mentions of the Intel eepro NICs. Are they best?
Processor: speeds probably don't matter too much (my Cisco 3640 router
    with 4 T1s has a 100Mhz processor, though it's RISC and has optimized IOS)
    but faster processors have faster FSB as well
Memory: 128 MB probably enough to deal with 100Mb?
HD: Obviously you want everything in memory, but if you're doing much
    logging you might get a solid-state disk.

I've done a little comparison testing of prebuilt firewall routers with a 
few little DLink/Sonicwall/Netgear boxes vs. an Athlon running IPCop, but 
I'm sure someone has done better hardware tests than mine. 
I'm open to any info. If I get enough for a good summary perhaps it could
be added to the HOWTO. 
Thanks.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-02-05 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 21:59 Joshua Daniel Franklin [this message]
2003-02-05 22:17 ` [LARTC] good hardware Robert Penz
2003-02-06  0:56 ` William L. Thomson Jr.

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=marc-lartc-104448243926562@msgid-missing \
    --to=joshua@iocc.com \
    --cc=lartc@vger.kernel.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.