Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Nicholas Erkert <nick@erkert.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] the "cisco vs. Linux" thread
Date: Thu, 08 Jul 2004 21:38:54 +0000	[thread overview]
Message-ID: <40EDBEEE.6080202@erkert.com> (raw)
In-Reply-To: <20040708193300.GA30890@mabeys.dsl.aros.net>

Glen Mabey wrote:
> On Thu, Jul 08, 2004 at 12:07:57PM -0400, Jos? Ildefonso Camargo Tolosa wrote:
> 
>>you can use an Athlon 
>>64 with DDR RAM and very good network hardware (that is very, very 
>>important)
> 
> 
> Regarding NICs, are there any recommendations out there for which
> manufacturers to go with?  I don't need anything faster than 100baseT.
> 
> I would think that Intel and 3Com would be in the "reliable" category,
> and RTL-based cards in the "forget it" category.
> 
> On the Intel note, I wonder what experience y'all have had with the two
> different drivers for the EtherExpressPro/100 card.  That is, eepro100
> versus e100.  I would think that noone would take the time to rewrite a
> driver if there wasn't anything wrong with the original one.
> 
> Thank you--
> Glen Mabey
> 
I have had some good luck with Intel cards using either drivers. I 
haven't noticed much difference between them but I haen't done a lot of 
stress testing on them.

On a side note has anyone built a linux router with dual/quad port 
ethernet cards (ie Intel PRO/1000 MT Quad Port Server Adapter)?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2004-07-08 21:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08 19:33 [LARTC] the "cisco vs. Linux" thread Glen Mabey
2004-07-08 21:38 ` Nicholas Erkert [this message]
2004-07-08 21:44 ` Nicholas Erkert
2004-07-09  9:47 ` Jeff Green
2004-07-09 14:35 ` Alfie Viechweg
2004-07-10 22:51 ` Glen Mabey
2004-07-10 23:25 ` Glen Mabey
2004-07-11  0:36 ` Dmitry Golubev
2004-07-11 14:48 ` S Mohan
2004-07-11 17:15 ` James Sneeringer
2004-07-11 18:48 ` José Ildefonso Camargo Tolosa
2004-07-12  7:18 ` przemolicc
2004-07-12  8:15 ` Abraham van der Merwe
2004-07-12  8:39 ` przemolicc
2004-07-12  9:33 ` przemolicc
2004-07-12 14:33 ` José Ildefonso Camargo Tolosa
2004-07-12 15:48 ` Ed Wildgoose
2004-07-12 16:01 ` José Ildefonso Camargo Tolosa
2004-07-13  7:22 ` Ed Wildgoose
2004-07-13 11:49 ` Alfie Viechweg
2004-07-13 13:44 ` Ed Wildgoose

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=40EDBEEE.6080202@erkert.com \
    --to=nick@erkert.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox