From owner-freebsd-net@FreeBSD.ORG Fri Mar 4 22:34:42 2005 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 6380F16A4CE for ; Fri, 4 Mar 2005 22:34:42 +0000 (GMT) Received: from angryfist.fasttrackmonkey.com (angryfist.fasttrackmonkey.com [216.223.196.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A19C643D2D for ; Fri, 4 Mar 2005 22:34:39 +0000 (GMT) (envelope-from spork@fasttrackmonkey.com) Received: (qmail 88522 invoked by uid 2003); 4 Mar 2005 22:29:09 -0000 Received: from spork@fasttrackmonkey.com by angryfist.fasttrackmonkey.com by uid 1001 with qmail-scanner-1.20 (clamscan: 0.65. Clear:RC:1(216.220.116.154):. Processed in 0.239148 secs); 04 Mar 2005 22:29:09 -0000 Received: from unknown (HELO localhost) (216.220.116.154) by 0 with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Mar 2005 22:29:08 -0000 Date: Fri, 4 Mar 2005 17:34:35 -0500 (EST) From: Charles Sprickman X-X-Sender: spork@oof.local To: freebsd-net@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: FreeBSD 4.x and OS-X tcp performance 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: Fri, 04 Mar 2005 22:34:42 -0000 Howdy, Sorry to bring what seems like a simple issue up here. I had been blaming slow afp filesharing between my OS-X (10.3.8 and previous) and FreeBSD 4.x boxes on netatalk's afp implementation for some time. Not too long ago I got frustrated with this and tried smb and then ftp. On a simple 10/100 network, and even with just a crossover between two boxes it seems that any tcp transfer tops out at around 250KB/s. On the same network using the same switch I can get near line-rate to an OpenBSD box and to another OS-X box. If I use nfs and force udp as the transport, I *do* get near line-rate between OS-X and FBSD. My 5.3 box is tanked at the moment, so I cannot tell if the problem happens there as well. I do have a full ADC account, so I will be testing with the latest Tiger preview shortly, and the ADC access does give me a decent bug reporting facility if the fault lies within the OS-X tcp stack. I'm no tcpdump wizard, would anyone care to help me track this down? Thanks, Charles