From owner-freebsd-net@FreeBSD.ORG Fri Aug 12 21:14:57 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 AC37216A41F for ; Fri, 12 Aug 2005 21:14:57 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5185143D48 for ; Fri, 12 Aug 2005 21:14:57 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id B28165D1B; Fri, 12 Aug 2005 17:14:56 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 39369-05; Fri, 12 Aug 2005 17:14:55 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id 202CC5C53; Fri, 12 Aug 2005 17:14:55 -0400 (EDT) Message-ID: <42FD1153.50202@mac.com> Date: Fri, 12 Aug 2005 17:14:59 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Miku Jha References: <20050812205736.26235.qmail@web50201.mail.yahoo.com> In-Reply-To: <20050812205736.26235.qmail@web50201.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: jha miku , freebsd-net@freebsd.org Subject: Re: Question regd timestamp option 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: Fri, 12 Aug 2005 21:14:57 -0000 Miku Jha wrote: [ ... ] > The situation is that if the client crashes, the server eventually sends a > RST (10.39.53) Following this RST, the client comes back in lets say around > 2-3 minutes. Now when the client sends a SYN(10.42.23), there is no > timestamp option. If the client opens a connection and both sides exchange packets with timestamps, you'll probably end up seeing "NNT" in all packets during the first session. This right? Now if you open a second connection, while things are still OK, do you see the SYN packet contain all options as normal? I assume the client is opening connections to the server? And it is a FreeBSD box...? Showing tcpdump data (or putting on a website somewhere) would help understand the issue... > Is there some requirement that RST needs to be ACKED > or RST flag will remain set for some time window > within which if SYN is send, timestamp option will not > be set. A RST to a closed or listening socket will be ignored (dropped), a RST which matches an established connection will flush and close that connection but will not be ACKed itself. -- -Chuck