From owner-freebsd-isp  Tue Jul  8 21:09:02 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA25483
          for isp-outgoing; Tue, 8 Jul 1997 21:09:02 -0700 (PDT)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA25478
          for <freebsd-isp@FreeBSD.ORG>; Tue, 8 Jul 1997 21:08:57 -0700 (PDT)
Received: (from danny@localhost)
	by panda.hilink.com.au (8.8.5/8.8.5) id OAA02672;
	Wed, 9 Jul 1997 14:08:39 +1000 (EST)
Date: Wed, 9 Jul 1997 14:08:39 +1000 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Robert Shady <rls@mail.id.net>
cc: support@netsonic.com, freebsd-isp@FreeBSD.ORG
Subject: Re: per-user IP accounting
In-Reply-To: <199707090334.XAA24690@server.id.net>
Message-ID: <Pine.BSF.3.91.970709140702.869v-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



> > > If I run netstat -abin, I get a list of all ip's but they are all the same,
> > > what needs to happen to breask that down for each particular ip?
> > 
> > netstat -aibn shows you the stats for the *interface*, with a separate 
> > line for each IP address of the interface.  If you have multiple IPs per 
> > interface, you need to use ipfw or something other than netstat.
> 
> Not to mention, the bytes wrap at a certain point too... We've pushed

True, and if you use netstat, you have to keep track of the previous 
value and adjust.  If you use ipfw, you can simply say 'ipfw -z zero' 
immediately after you read the values each hour/day/week.

Danny