From owner-freebsd-net@FreeBSD.ORG  Fri Jun 27 12:32:43 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DC8EE37B401
	for <freebsd-net@freebsd.org>; Fri, 27 Jun 2003 12:32:43 -0700 (PDT)
Received: from mail.buzzardnews.com (mail.buzzardnews.com [64.235.227.35])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7151843F3F
	for <freebsd-net@freebsd.org>; Fri, 27 Jun 2003 12:32:41 -0700 (PDT)
	(envelope-from shawn@cpl.net)
Received: from shawn ([216.117.221.133])
	by mail.buzzardnews.com (8.11.3/8.11.3) with SMTP id h5RJWf473886
	for <freebsd-net@freebsd.org>; Fri, 27 Jun 2003 12:32:41 -0700 (PDT)
Message-ID: <007101c33ce2$657e7e50$85dd75d8@shawn>
From: "Shawn Ramsey" <shawn@cpl.net>
To: <freebsd-net@freebsd.org>
References: <BB21E605.155C1%mksmith@noanet.net>
Date: Fri, 27 Jun 2003 12:29:15 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: Re: Lots of input errors... 
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2003 19:32:44 -0000

> Hello:
>
> Judging from your output I would say two things:
>
> 1) You have a bad cable.  CRC and framing errors are usually a result of
bad
> media.
> 2) You should set the port to auto/auto, not 100/Full hard set, unless you
> have specifically set that up in rc.conf.  If one side is hard set and the
> other is set to auto, you will see lots of runts because of a duplex
> mismatch.  I think the RFC states you have to go to half duplex if you are
> autosensing and the other side doesn't respond, which is the case if it's
> hard set.

Ok.. It is set hard to 100BT/FD on both ends. I don't know if you saw this,
but since resetting the stats a few hours ago, it shows no errors at all on
their end, but were still getting errors on our end... The CRC and frame
errors could have been from a media mismatch when things were first setup.
Im not sure if the stats have ever been reset. Assuming the errors stay at
zero on their end, any ideas? Am going to try another server/router, and if
things look better, start replacing hardware on this router...