From owner-freebsd-hackers Wed Mar 25 12:26:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25913 for freebsd-hackers-outgoing; Wed, 25 Mar 1998 12:26:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25848 for ; Wed, 25 Mar 1998 12:25:47 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id MAA13008; Wed, 25 Mar 1998 12:25:39 -0800 (PST) Message-Id: <199803252025.MAA13008@implode.root.com> To: Arman Hazairin Hasan cc: freebsd-hackers@FreeBSD.ORG Subject: Re: TCP connection hang In-reply-to: Your message of "Thu, 26 Mar 1998 03:20:52 +0700." From: David Greenman Reply-To: dg@root.com Date: Wed, 25 Mar 1998 12:25:39 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >So, is it mean that SCO implementation has problem, or just wrong setup >> >in >> >that SCO box ? >> >> I think the problem is with the routers and not the computers. > >If the problem in the routers, why can i transfer 1.8MB of >uuencoded file without any problem. Doesnt it suppose to do >retransmission instead of just keep silent ? As was pointed out by Peter, the FreeBSD machine is getting the packets (and BPF is showing them), but they are discarded at the TCP level because of the bad checksum. The corruption appears to be sensitive to the packet contents, so that is why some things work and others do not. >Maybe I should compare the tcpdump output of both side, and do \ >packet dump (option x?) so we can lookup into tcp checksum. And >see where the packet has been hamperred. Yes, this might help, but it may only confirm what is already known - that the packet data is corrupted in some strange way. >Or maybe I just put FreeBSD box as a replacement for SCO :) >Seems like good idea, anyone ? That will only help if the corruption is occuring due to a software problem in the SCO machine. I don't think that is where the problem is; I think it is with the routers or the 64Kbps circuit between them. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message