From owner-freebsd-net@FreeBSD.ORG Wed Apr 4 10:13:17 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60F16106564A for ; Wed, 4 Apr 2012 10:13:17 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id C33568FC0A for ; Wed, 4 Apr 2012 10:13:16 +0000 (UTC) Received: (qmail 30789 invoked from network); 4 Apr 2012 10:11:23 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 4 Apr 2012 10:11:23 -0000 Message-ID: <4F7C1EB9.5060307@freebsd.org> Date: Wed, 04 Apr 2012 12:13:13 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: perryh@pluto.rain.com References: <4F75C1A3.4030401@freebsd.org> <4F75D9ED.7080707@freebsd.org> <4F780373.6030107@freebsd.org> <4F7AFEEF.60708@freebsd.org> <4F7B1981.1050009@freebsd.org> <4F7B3098.3090901@freebsd.org> <4f7c62c7.MUlfd0e/uNQsAVZG%perryh@pluto.rain.com> In-Reply-To: <4f7c62c7.MUlfd0e/uNQsAVZG%perryh@pluto.rain.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: darrenr@freebsd.org, freebsd-net@freebsd.org Subject: Re: FreeBSD TCP ignores zero window size X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Apr 2012 10:13:17 -0000 On 04.04.2012 17:03, perryh@pluto.rain.com wrote: > Andre Oppermann wrote: > >> The other side is retransmitting data we have already received >> and acknowledged ... That behavior is totally non-compliant. > > Any chance our ack of that data got dropped/lost enroute, and the > other side is resending after timing out? The correct ACK is retransmitted about a dozen times for re-synchronization. Unlikely that all of them get lost. On top of it the RST to terminate the session has the correct SEQ. Something's munging the SEQ/ACK space along the way here. -- Andre