From owner-freebsd-current Fri Sep 22 05:59:09 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA28333 for current-outgoing; Fri, 22 Sep 1995 05:59:09 -0700 Received: from alpha.netcraft.co.uk ([194.72.238.8]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA28318 ; Fri, 22 Sep 1995 05:59:05 -0700 Received: (from paul@localhost) by alpha.netcraft.co.uk (8.6.11/8.6.9) id NAA07347; Fri, 22 Sep 1995 13:56:25 +0100 From: Paul Richards Message-Id: <199509221256.NAA07347@alpha.netcraft.co.uk> Subject: Re: IP accounting To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 22 Sep 1995 13:56:25 +0100 (BST) Cc: gary@palmer.demon.co.uk, nathan@netrail.net, questions@FreeBSD.org, current@FreeBSD.org In-Reply-To: <21681.811764710@time.cdrom.com> from "Jordan K. Hubbard" at Sep 22, 95 03:11:50 am Reply-to: paul@netcraft.co.uk X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 928 Sender: owner-current@FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who said > > > As for kilobytes/interface, I dunno if that's possible without using > > some sort of packet sniffer. > > Couldn't you just use the output from `netstat -ib' in a slow loop to > essentially approximate that functionality? I don't know what kind of > granularity is required, but David was able to meter wcarchive's > bytes/sec traffic fairly well by doing that repeatedly. ipfw accounting gives the stats you need. If we ditch ipfw (and I tend to be in favour) then I really hope we can retain accurate ip traffic accounting because that's essential to the way we use it on our boxes. Netstat simply doesn't do the job since it measures traffic per interface and I have a number of virtual hosts and need traffic per ip address. -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work)