From owner-freebsd-current Thu Mar 2 9: 3:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id AF4B937BBE2 for ; Thu, 2 Mar 2000 09:03:16 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id LAA59035; Thu, 2 Mar 2000 11:03:01 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200003021703.LAA59035@celery.dragondata.com> Subject: Re: lo0 tcp connections in TIME_WAIT/LAST_ACK/FIN_WAIT? To: shin@nd.net.fujitsu.co.jp (Yoshinobu Inoue) Date: Thu, 2 Mar 2000 11:02:55 -0600 (CST) Cc: toasty@dragondata.com, current@FreeBSD.ORG In-Reply-To: <20000302113536C.shin@nd.net.fujitsu.co.jp> from "Yoshinobu Inoue" at Mar 02, 2000 11:35:36 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 > Right now, it only seems to be happening for bbd (part of /usr/ports/net/bb), when local connections are talking to bbd. (I moved bbd to port 4242, it's default is port 1984) Doing an ifconfig lo0 down ; ifconfig lo0 up seems to have cleared them, too. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message