From: J Sloan <joe@tmsusa.com>
To: law@tlinx.org
Cc: janvapan <jvp@wanadoo.es>, linux-kernel@vger.kernel.org
Subject: Re: Recommendations about a 100/10 NIC
Date: Sun, 03 Mar 2002 17:04:08 -0800 [thread overview]
Message-ID: <3C82C808.8040304@tmsusa.com> (raw)
In-Reply-To: <NFBBKNPJLGIDJFAHGKMBEENKCBAA.law@tlinx.org>
LA Walsh @ tlinx.org wrote:
>Any recommendations for the most Linux-friendly/best performance,
>2-ethernet port cards? Is there a website one could go to find Linux
>Compatible and Linux-ease-of-use hardware and software products? Comparisons?
>
Hmm, the only multiport cards I've used are
some tlans and some intel pro 100s -
The tlans are no good for serious use, at least
in my experience - I've been replacing them
as replacements are available.
The dual intel 10/100s I've used work fine,
they are simply detected as 2 intel ethernet
devices.
Joe
next prev parent reply other threads:[~2002-03-04 1:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-03 12:18 Recommendations about a 100/10 NIC janvapan
2002-03-03 14:22 ` Justin Piszcz
2002-03-03 20:29 ` Bernd Eckenfels
2002-03-03 21:04 ` Hans-Christian Armingeon
2002-03-04 3:05 ` rddunlap
2002-03-03 21:37 ` Hans-Christian Armingeon
2002-03-03 17:15 ` J Sloan
2002-03-03 20:39 ` LA Walsh @ tlinx.org
2002-03-04 1:04 ` J Sloan [this message]
2002-03-07 8:21 ` Kelsey Hudson
2002-03-06 17:15 ` Ken Brownfield
2002-03-06 17:36 ` John Jasen
2002-03-06 17:28 ` Tim Hockin
2002-03-06 18:30 ` Michael Sterrett -Mr. Bones.-
2002-03-06 18:33 ` John Jasen
2002-03-06 21:42 ` Francois Romieu
2002-03-08 1:47 ` Ken Brownfield
2002-03-07 5:06 ` J Sloan
2002-03-07 8:16 ` Kelsey Hudson
[not found] <Pine.LNX.4.10.10203031559090.801-100000@oakley.chf>
2002-03-03 16:25 ` Justin Piszcz
2002-03-04 5:15 ` Mike Fedyk
2002-03-04 9:54 ` Vojtech Pavlik
[not found] <fa.fifmv4v.ogc1qa@ifi.uio.no>
[not found] ` <fa.jgnh1iv.1ek48ih@ifi.uio.no>
2002-03-04 6:49 ` Dan Maas
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=3C82C808.8040304@tmsusa.com \
--to=joe@tmsusa.com \
--cc=jvp@wanadoo.es \
--cc=law@tlinx.org \
--cc=linux-kernel@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.