From owner-freebsd-net@FreeBSD.ORG Wed Mar 17 00:00:07 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 4BCD316A4CE for ; Wed, 17 Mar 2004 00:00:07 -0800 (PST) Received: from demos.su (mx.demos.su [194.87.0.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CB4C43D41 for ; Wed, 17 Mar 2004 00:00:06 -0800 (PST) (envelope-from tolyar@mx.ru) Received: from [194.87.2.159] (HELO dwarf.demos.su) by demos.su (CommuniGate Pro SMTP 4.1.8/D) with SMTP id 179751335; Wed, 17 Mar 2004 11:00:05 +0300 Date: Wed, 17 Mar 2004 11:00:05 +0300 From: Zherdev Anatoly To: cjclark@alum.mit.edu Message-Id: <20040317110005.3925a22a@dwarf.demos.su> In-Reply-To: <20040317073956.GA52536@blossom.cjclark.org> References: <20040316125335.5f64cac5@dwarf.demos.su> <20040317000611.GA51156@blossom.cjclark.org> <20040317101453.5fcdaa82@dwarf.demos.su> <20040317073956.GA52536@blossom.cjclark.org> X-Mailer: Sylpheed version 0.9.9claws (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: cristjc@comcast.net Subject: Re: Problem with closing tcp session between cisco and freebsd 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: Wed, 17 Mar 2004 08:00:07 -0000 On Tue, 16 Mar 2004 23:39:56 -0800 "Crist J. Clark" wrote: > But it looks like my guess is probably correct. The receive buffer at > the FreeBSD end is full. When it receives more TCP data, it cannot > accept it so it ACKs up to whatever it has in the buffer and not what > the sender sent in the last segment. It also sends a window size of > zero to tell the sender it's not accepting more data at the moment. > > You need to flush the buffer at the FreeBSD end. The program receiving > on that socket needs to read the data. If the process is frozen, kill > it and things should clear up. OK. Thak you. I will find problems in programs. -- Zherdev Anatoly.