From owner-freebsd-net@FreeBSD.ORG  Mon Mar  8 18:19:48 2004
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 B155516A4D0
	for <freebsd-net@freebsd.org>; Mon,  8 Mar 2004 18:19:48 -0800 (PST)
Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A69C943D53
	for <freebsd-net@freebsd.org>; Mon,  8 Mar 2004 18:19:48 -0800 (PST)
	(envelope-from wes@softweyr.com)
Received: from salty.rapid.stbernard.com (unknown [198.147.128.71])
	by smtp-relay.omnis.com (Postfix) with ESMTP
	id 4C8231880401; Mon,  8 Mar 2004 18:19:47 -0800 (PST)
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr.com
To: "Marc G. Fournier" <scrappy@hub.org>
Date: Mon, 8 Mar 2004 18:19:26 -0800
User-Agent: KMail/1.5.4
References: <20040306150504.Q13247@ganymede.hub.org>
	<Pine.BSF.4.58.0403061733200.12479@manganese.bos.dyndns.org>
	<20040307193726.R13247@ganymede.hub.org>
In-Reply-To: <20040307193726.R13247@ganymede.hub.org>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200403081109.20032.wes@softweyr.com>
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
cc: freebsd-net@freebsd.org
Subject: Re: Odd network issue ... *very* slow scp between two servers
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: Tue, 09 Mar 2004 02:19:48 -0000

On Sunday 07 March 2004 15:37, Marc G. Fournier wrote:
>
> Note that forcing it to 100baseT half-duplex (or 10baseT/UTP half-duplex)
> corrects the problem ... turns out it is only in full-duplex mode that
> its hosed ...

Did you try a cross-over cable?  Actually, you shouldn't even need a 
cross-over cable for gigabit devices, they should auto-select MDI vs. MDIX.

Also, I recall reading something about problems with onboard tx cksum errors 
on em devices recently; you may want to turn off the tx cksum feature in 
your testing.  Or search the archives for txcsum or something like that.

-- 
         "Where am I, and what am I doing in this handbasket?"

Wes Peters                                              wes@softweyr.com