From owner-freebsd-current  Fri Apr 30 10:30:45 1999
Delivered-To: freebsd-current@freebsd.org
Received: from misha.cisco.com (misha.cisco.com [171.69.206.50])
	by hub.freebsd.org (Postfix) with ESMTP id BADD914BD2
	for <current@freebsd.org>; Fri, 30 Apr 1999 10:30:42 -0700 (PDT)
	(envelope-from mi@misha.cisco.com)
Received: (from mi@localhost)
	by misha.cisco.com (8.9.2/8.9.1) id NAA26434
	for current@freebsd.org; Fri, 30 Apr 1999 13:30:41 -0400 (EDT)
	(envelope-from mi)
Message-Id: <199904301730.NAA26434@misha.cisco.com>
Subject: Re: ep0 *UTP*
In-Reply-To: <xzpzp3qvx7c.fsf@flood.ping.uio.no> from Dag-Erling Smorgrav at "Apr 30, 1999 07:23:51 pm"
To: current@freebsd.org
Date: Fri, 30 Apr 1999 13:30:41 -0400 (EDT)
Reply-To: mi@aldan.algebra.com
From: Mikhail Teterin <mi@aldan.algebra.com>
X-Mailer: ELM [version 2.4ME+ PL52 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dag-Erling Smorgrav once wrote:

> > > > Well, I'd chalk  it up to buggy 3com h/w  myself. Alas I'm still
> > > > getting: ep0 XXX: driver didn't set ifq_maxlen
> > > I still get that one too.  Driver problem?
> > I'm guessing so. I  wonder if this is the cause  of some odd network
> > behavior I'm getting..
> 
> Anybody using  a 3c509  and expecting  it to  work reliably  should be
> taken out and shot in the back of the head.

Is this because the  cards are bad, or because the driver  is bad? I had
my share of problems with them, until I set them to use MTU of 900 -- no
problems since, with NFS and  X-session traffic flowing through the pair
of this cards.

	-mi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message