From owner-freebsd-net@FreeBSD.ORG Tue Jun 20 06:02:59 2006 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 4FB8416A47A for ; Tue, 20 Jun 2006 06:02:59 +0000 (UTC) (envelope-from Susan.Lan@zyxel.com.tw) Received: from zyadd226.zyxel.com.tw (zyadd226.zyxel.com.tw [61.222.65.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE92943D45 for ; Tue, 20 Jun 2006 06:02:56 +0000 (GMT) (envelope-from Susan.Lan@zyxel.com.tw) Received: from zytwbe01.zyxel.com ([172.23.5.10]) by smtp.zyxel.com.tw with InterScan Messaging Security Suite; Tue, 20 Jun 2006 14:11:04 +0800 Received: from zytwfe01.ZyXEL.com ([172.23.5.5]) by zytwbe01.zyxel.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Jun 2006 14:02:52 +0800 Received: from [172.23.18.2] ([172.23.18.2]) by zytwfe01.ZyXEL.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Jun 2006 14:02:51 +0800 Message-ID: <44978F16.9010005@zyxel.com.tw> Date: Tue, 20 Jun 2006 14:00:54 +0800 From: Blue User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Jun 2006 06:02:52.0011 (UTC) FILETIME=[2A43FBB0:01C6942F] Subject: TIME_WAIT state check in in_pcblookup_local() 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: Tue, 20 Jun 2006 06:02:59 -0000 Hi, All: I have a doubt in in_pcblookup_local() and in6_pcblookup_local() functions in in_pcb.c/in6_pcb.c in FreeBSD-6.1RELEASE. In v4 version (that is, in_pcblookup_local), the inp would be checked to see if the prospective port is used in TCP TIME_WAIT state. If so, it will call tcp_twrecycleable() to see if recycling is possible. However, I noticed that in v6 version (that is, in6_pcblookup_local) would not do such examination. In my opinion, the check should be removed since the connection is still alive in TIME_WAIT state and the port number should be considered unavailable. Best regards, blue