From owner-freebsd-bugs Mon Sep 20 3: 0: 6 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id C72FF151A6 for ; Mon, 20 Sep 1999 03:00:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id DAA43103; Mon, 20 Sep 1999 03:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 20 Sep 1999 03:00:02 -0700 (PDT) Message-Id: <199909201000.DAA43103@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ruslan Ermilov Subject: Re: misc/12252: netstat fails to display TCP connectoins Reply-To: Ruslan Ermilov Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/12252; it has been noted by GNATS. From: Ruslan Ermilov To: jrd@cc.usu.edu Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/12252: netstat fails to display TCP connectoins Date: Mon, 20 Sep 1999 12:49:17 +0300 On Wed, Jun 16, 1999 at 07:02:31PM -0700, jrd@cc.usu.edu wrote: > > netstat shows UDP and Unix but not TCP connections. The problem is > the TCP protocol value is not set in the xt_socket structure > passed back to netstat routines. See horrid workaround below (one > line). The value returned in the structure looks rather like an > address or left over un-inited garbage. > I can't reproduce your problem on neither 3.2-RELEASE nor 3.3-RELEASE. tcp_pcblist() sysctl correctly calls sotoxsocket(), which certainly fills in `xso_protocol' field. If the problem still exist, could you please provide some additional details, e.g. the output of `netstat -n -finet' while TCP sockets are in use? Thanks, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message