From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 15:37:55 2004 Return-Path: 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 93E2516A4CE for ; Sun, 7 Mar 2004 15:37:55 -0800 (PST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 687CF43D2F for ; Sun, 7 Mar 2004 15:37:55 -0800 (PST) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id 17C7334504; Sun, 7 Mar 2004 19:37:56 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 16CED344FB; Sun, 7 Mar 2004 19:37:56 -0400 (AST) Date: Sun, 7 Mar 2004 19:37:56 -0400 (AST) From: "Marc G. Fournier" To: Tim Wilde In-Reply-To: Message-ID: <20040307193726.R13247@ganymede.hub.org> References: <20040306150504.Q13247@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 23:37:55 -0000 On Sat, 6 Mar 2004, Tim Wilde wrote: > On Sat, 6 Mar 2004, Marc G. Fournier wrote: > > > I have two servers on the same network switch, sitting one on top of the > > other ... one is running an em (Dual-Xeon 2.4Ghz) device, the other an fxp > > (Dual-PIII 1.3Ghz) device ... > > Is it a Cisco Catalyst switch? If so, you need to switch the em's to > autoselect, on both the server and switch end. For some reason, the em > driver will not properly lock down its rate when talking to a Cisco > Catalyst switch. At least, I had an identical problem with em's talking > to a Catalyst 2950 and that was the fix I came up with. Give it a try and > see how your results go. 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 ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664