From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 20:12:38 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 AE41C16A4CE for ; Sun, 18 Jan 2004 20:12:38 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id CE94743D48 for ; Sun, 18 Jan 2004 20:12:36 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 26879 invoked from network); 19 Jan 2004 04:12:36 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 19 Jan 2004 04:12:36 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sun, 18 Jan 2004 22:12:34 -0600 (CST) From: Mike Silbersack To: CHOI Junho In-Reply-To: <20040115.224407.41715339.cjh@kr.FreeBSD.org> Message-ID: <20040118220617.P5672@odysseus.silby.com> References: <20040113.225411.74714267.cjh@kr.FreeBSD.org> <20040115.224407.41715339.cjh@kr.FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: FreeBSD -> Windows HTTP 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: Mon, 19 Jan 2004 04:12:38 -0000 On Thu, 15 Jan 2004, CHOI Junho wrote: > For those who interested, I made packet dump file: > > http://www.kr.freebsd.org/~cjh/misc/freebsd-net/ > > Best thing is do tcpdump at client machine but I have no admin > permission, so failed. > > -- > CHOI Junho KFUG I can read these fine, Andre must be going through some web proxy that corrupts them. :) All of the computers in the dumps are on a LAN, right? There seems to be quite a bit of packet loss going on, from what I can see. This is most certainly the cause of low throughput; we'd need tcpdumps from both ends to really determine if there's some suboptimal tcp interaction between w2k and freebsd. (From a single side of the connection, we can't even be sure if retransmissions are getting through, etc.) Mike "Silby" Silbersack