From owner-freebsd-hackers Wed Mar 25 11:03:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10113 for freebsd-hackers-outgoing; Wed, 25 Mar 1998 11:03:15 -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 LAA10105 for ; Wed, 25 Mar 1998 11:03:05 -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 LAA12049; Wed, 25 Mar 1998 11:02:49 -0800 (PST) Message-Id: <199803251902.LAA12049@implode.root.com> To: Peter Edwards cc: Arman Hazairin , freebsd-hackers@FreeBSD.ORG Subject: Re: TCP connection hang In-reply-to: Your message of "Wed, 25 Mar 1998 13:17:26 GMT." <351903E6.FB041AEC@isocor.ie> From: David Greenman Reply-To: dg@root.com Date: Wed, 25 Mar 1998 11:02:49 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Btw, I convert the binary file that i want to transmit into text using >> uuencode, and finaly i can transfer the file. >> But still no answer for this 'strange' behaviour. > >I hear a bell ringing in the distance. >This indicates that the problem is not related to the size of the data, but its >content. If the data-link path wasn't 8-bit clean (say, the SCO terminal device >was doing cr->cr-lf translations on the TCP packets for example), is it >possible that tcpdump shows the incoming (corrupted) packets coming up through >bpf but the TCP code discards them because the checksum is invalid? This would >explain why the FreeBSD box apparently "sees" the incoming packet, but the TCP >stack doesn't respond to it. If this is the case, then an examination of the 'netstat -s' stats should show this...Arman? -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