From owner-freebsd-isp Sun Sep 23 0:13:59 2001 Delivered-To: freebsd-isp@freebsd.org Received: from home.com (c1737881-a.plano1.tx.home.com [65.10.46.29]) by hub.freebsd.org (Postfix) with ESMTP id 0302037B413; Sun, 23 Sep 2001 00:13:53 -0700 (PDT) Received: (from mcbrune@localhost) by home.com (8.11.6/8.11.4) id f8N7Dph01844; Sun, 23 Sep 2001 02:13:51 -0500 (CDT) (envelope-from mcbrune) From: mcbrune Message-Id: <200109230713.f8N7Dph01844@home.com> Subject: Re: so many TIME_WAIT, FIN_WAIT_1, FIN_WAIT_2 In-Reply-To: <00c301c14237$b00c11a0$125131ce@wavephil.com> To: Jun Favoreal Date: Sun, 23 Sep 2001 02:13:51 -0500 (CDT) Cc: freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL92 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have not seen this on FreeBSD, but I have seen something like this on Sun. Are you sure these *_WAITs never go away, and are replaced by other WAITs? The default for TIME_WAIT is 4 minutes. Corey [ Charset ISO-8859-1 unsupported, converting... ] > > Hello, > > This is my setup. I have a transparent proxy server running SQUID2.4-STABLE2 > on a FreeBSD box running 4.3-RELEASE. As any transparent proxy out there, > HTTP requests are intercepted by our primary router and redirected to the > FreeBSD box and the FreeBSD box hijacks it and makes the HTTP connection in > behalf of the hijacked HTTP request. Everything is working just fine. But, > just one observation from the FreeBSD box if you do a > > # netstat -an > > I see so many tcp socket connections in either FIN_WAIT_1, FIN_WAIT_2, or > TIME_WAIT status. > > > tcp4 0 0 199.172.146.99.80 202.58.248.20.3108 > FIN_WAIT_1 > tcp4 0 0 64.4.13.171.80 202.58.248.20.3106 > FIN_WAIT_2 > tcp4 0 0 206.49.81.19.24737 207.25.71.212.80 TIME_WAIT > tcp4 0 0 64.38.209.154.80 202.58.248.20.3099 > FIN_WAIT_2 > tcp4 0 0 216.136.172.223.80 202.58.253.254.3894 TIME_WAIT > tcp4 0 0 64.38.209.154.80 202.58.248.20.3095 > FIN_WAIT_2 > tcp4 0 0 216.115.106.35.80 202.58.248.20.3092 > FIN_WAIT_2 > tcp4 0 0 216.136.173.152.80 202.58.247.204.3265 TIME_WAIT > tcp4 0 0 216.136.173.152.80 202.58.247.204.3263 TIME_WAIT > tcp4 0 0 207.68.177.124.80 202.58.248.20.3090 > FIN_WAIT_2 > tcp4 0 0 64.58.76.229.80 202.58.247.211.1400 TIME_WAIT > tcp4 0 0 209.85.3.8.80 202.58.248.20.3088 > FIN_WAIT_2 > > > Previously I have setup 2 other transparent proxy servers running FreeBSD > 3.3-RELEASE and I see the same thing. Once its there, it stays there and > each day its number grows. So what I do from time to time is to shutdown the > FreeBSD box and boot it again just to remove these things and start over > with a clean slate. I have also tried some tweaking in SQUID, most of them > decreasing the timeout values like connect_timeout, read_timeout, > request_timeout, pconn_timeout, and client_lifetime. > > Anyone out there who had this problem before ??? > > Thank you in advance. > > -- > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message