From owner-freebsd-net Fri Dec 14 5:46:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id E624437B417 for ; Fri, 14 Dec 2001 05:46:18 -0800 (PST) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id fBEDkHN45695 for freebsd-net@freebsd.org; Fri, 14 Dec 2001 07:46:17 -0600 (CST) (envelope-from tinguely) Date: Fri, 14 Dec 2001 07:46:17 -0600 (CST) From: mark tinguely Message-Id: <200112141346.fBEDkHN45695@web.cs.ndsu.nodak.edu> To: freebsd-net@freebsd.org Subject: Re: TCP snd_recover Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Sorry, I lost my negatives this morning ... we can NOT do much about stale snd_recover, and would NOT happen very easilly, NOR often. initialization for the snd_recover TCPS_SYN_SENT and TCPS_SYN_RECEIVED is a simple solution that can handle the simple case, and much more likely case. --mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message