public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Golds <jgolds@resilience.com>
To: "Michael H. Warfield" <mhw@wittsend.com>
Cc: Harald Welte <laforge@gnumonks.org>,
	Fabbione <fabbione@fabbione.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OFF-TOPIC] 4 ports ETH cards
Date: Wed, 30 May 2001 15:25:34 -0700	[thread overview]
Message-ID: <3B15735E.5781700F@resilience.com> (raw)
In-Reply-To: <3B135549.19CF8965@fabbione.net> <20010530183416.P14293@corellia.laforge.distro.conectiva> <20010530180344.A5304@alcove.wittsend.com>

"Michael H. Warfield" wrote:
> 
> On Wed, May 30, 2001 at 06:34:16PM -0300, Harald Welte wrote:
> > On Tue, May 29, 2001 at 09:52:41AM +0200, Fabbione wrote:
> > > Hi all,
> > >     sorry for the offtopic msg.
> > >
> > > Can someone point me to a 4 ports fast/eth card solution for linux?
> 
> > D-Link DFE-570 has a reasonable pricing and is well supported by the
> > tulip driver
> 
>         Just got three of these suckers and I'm about to order a bunch
> more (happy camper)...
> 
> > > I found some cards based on the DEC 21*4* chips but when
> > > I asked for more details I got a strange answer from the reseller
> > > like that this card is able to work only half-duplex and the chip has
> > > only one mac-address for the 4 eth cards (really strange).
> 
> > nah. And even if so, you can always change the mac-address using ifconfig.
> 
>         Each D-Link card has four MAC addresses (sequential).  I doubt
> other manufactures are any different.
> 
> > What the guy most likely wanted to say, is that there is only one EEprom
> > containing all mac adresses for the four tulip chips, which I have seen
> > on multiple boards
> 
>         What the guy was doing was having a bad case of optical rectitus.
> That would be typical of a "reseller" (AKA Salesman).  Most would not
> even have a CLUE that the cards were based on the tulip chipset / driver.
> 
>         Because the D-Link cards were less than half of the nearest
> competitor [ < $180 vs > $360 for others and Compac was > $2400! ] I
> ordered only three not knowing for sure if they would work.  Turned on
> the tulip driver and them suckers fired right up.  Now I know they work,
> stock, right out of the box, and I can order a bunch more for the lab
> I'm working with.
> 

I've been working with these boards for a couple months and thought they
were great.  However, now it turns out that they won't fit into our
systems too well (a little too long).  Does anyone have knowledge of
another brand that has a (slightly) smaller form factor?  I did some
checking on Pricewatch but wasn't able to find anything that fit our
needs.

TIA,

-Jeff

-- 
Jeff Golds
jgolds@resilience.com

  reply	other threads:[~2001-05-30 22:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29  7:52 [OFF-TOPIC] 4 ports ETH cards Fabbione
2001-05-29 13:05 ` J . A . Magallon
2001-05-29 19:21 ` Dan Hollis
2001-05-30  5:27   ` Fabbione
2001-05-30 21:34 ` Harald Welte
2001-05-30 22:03   ` Michael H. Warfield
2001-05-30 22:25     ` Jeff Golds [this message]
2001-05-31  0:23       ` George Bonser
2001-05-30 22:57     ` Martin Josefsson
2001-05-31  5:21     ` Fabbione
2001-05-31 12:03     ` poptix

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=3B15735E.5781700F@resilience.com \
    --to=jgolds@resilience.com \
    --cc=fabbione@fabbione.net \
    --cc=laforge@gnumonks.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhw@wittsend.com \
    /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