From owner-freebsd-current Mon Dec 24 9:51: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 11DC937B417; Mon, 24 Dec 2001 09:50:56 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fBOHopD29878; Mon, 24 Dec 2001 12:50:52 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 24 Dec 2001 12:50:51 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Martin Blapp Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: netstat -f inet broken ? In-Reply-To: <20011224135729.X979-100000@levais.imp.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 24 Dec 2001, Martin Blapp wrote: > As we just have noted, there is no output anymore for netstat -f inet. > Has the support been dropped ? > > Also there are only unix domain sockets in the normal netstat output. I > cannot see any tpc4 connections anymore. > > I noted this in 4.5 PRERELEASE too. It used to work in 4.3 RELEASE and > 4.4 RELEASE. > > So it got broken trough a MFC between 4.4 and 4.5. > > I think this is important for security reasons ! Verify that your userland and kernel are in sync, and let us know if the problem persists. A few people ran into this, but it cleared up for all of them when they re-sync'd userland and kernel. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message