From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 14 Jun 2001 23:51:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 14 Jun 2001 23:51:08 -0400 Received: from sense-robertk-129.oz.net ([216.39.160.129]:18305 "HELO mail.kleemann.org") by vger.kernel.org with SMTP id ; Thu, 14 Jun 2001 23:51:00 -0400 Date: Thu, 14 Jun 2001 20:50:55 -0700 (PDT) From: Robert Kleemann X-X-Sender: To: Subject: Re: Client receives TCP packets but does not ACK In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org A couple people have requested a test case. The problem first showed up in a very large java app. Since then I wrote a small perl program to duplicate the behavior of the large app by sending the same data, in the same order, in the same sized blocks, from the server to the client. If you want to test this on your configuration then download the following two files: http://www.kleemann.org/crap/clientserver http://www.kleemann.org/crap/log1e1.txt Place a copy of the files in the same directory on both the client and the server and run the program the following way: [server]$ ./clientserver -s log1e1.txt listening on port 20001 [client]$ ./clientserver -c serverhostname log1e1.txt The server will attempt to send the data to the client which then verifies each byte received. My client generally stops ack-ing between messages 15 and 25. Robert.