From owner-freebsd-current Wed Mar 1 18:34:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 87BA837BFC1 for ; Wed, 1 Mar 2000 18:34:50 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id LAA26196; Thu, 2 Mar 2000 11:34:44 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id LAA14318; Thu, 2 Mar 2000 11:34:44 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id LAA23726; Thu, 2 Mar 2000 11:34:43 +0900 (JST) To: toasty@dragondata.com Cc: current@FreeBSD.ORG Subject: Re: lo0 tcp connections in TIME_WAIT/LAST_ACK/FIN_WAIT? In-Reply-To: <200002290552.XAA45164@celery.dragondata.com> References: <200002290552.XAA45164@celery.dragondata.com> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000302113536C.shin@nd.net.fujitsu.co.jp> Date: Thu, 02 Mar 2000 11:35:36 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 35 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After upgrading from 3.4 to RC2, i'm noticing something that I never saw > before: > > Active Internet connections (including servers) > Proto Recv-Q Send-Q Local Address Foreign Address (state) > tcp 0 0 127.0.0.1.4954 127.0.0.1.4242 SYN_SENT > tcp 0 0 127.0.0.1.4953 127.0.0.1.4242 TIME_WAIT > tcp 0 0 127.0.0.1.4952 127.0.0.1.4242 TIME_WAIT > tcp 0 0 127.0.0.1.4951 127.0.0.1.4242 TIME_WAIT > tcp 0 0 127.0.0.1.4950 127.0.0.1.4242 TIME_WAIT > tcp 0 0 127.0.0.1.4949 127.0.0.1.4242 TIME_WAIT > tcp 0 0 127.0.0.1.4948 127.0.0.1.4242 LAST_ACK > tcp 0 0 127.0.0.1.4947 127.0.0.1.4242 CLOSE_WAIT > tcp 0 0 127.0.0.1.4945 127.0.0.1.4242 TIME_WAIT > tcp 0 0 127.0.0.1.4944 127.0.0.1.4242 TIME_WAIT > tcp 0 0 127.0.0.1.4942 127.0.0.1.4242 TIME_WAIT > tcp 0 0 127.0.0.1.4940 127.0.0.1.4242 FIN_WAIT_1 > tcp 0 0 127.0.0.1.4938 127.0.0.1.4242 FIN_WAIT_1 > tcp 0 0 127.0.0.1.4937 127.0.0.1.4242 TIME_WAIT > tcp 0 0 127.0.0.1.4936 127.0.0.1.4242 TIME_WAIT > > > Are tcp connections going through lo0 ever supposed to end up like this? I > thought everything that went through lo0 was supposed to be.. well.. > instant and mostly lossless. Any ideas? > > Kevin Hi, does that happen for any apps? Could you please give me info about what is the apps which use the port 4242? Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message