From owner-freebsd-hackers Tue Jun 9 08:44:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22285 for freebsd-hackers-outgoing; Tue, 9 Jun 1998 08:44:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22175 for ; Tue, 9 Jun 1998 08:43:41 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.8/8.8.8) with SMTP id IAA11732; Tue, 9 Jun 1998 08:43:29 -0700 (PDT) (envelope-from ejs@bfd.com) Date: Tue, 9 Jun 1998 08:43:29 -0700 (PDT) From: "Eric J. Schwertfeger" To: Dave Siegel cc: robert@cyrus.watson.org, tsecula@cisco.com, freebsd-hackers@FreeBSD.ORG Subject: Re: isp billing s/w In-Reply-To: <199806091531.IAA06977@seagull.rtd.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Jun 1998, Dave Siegel wrote: > I don't know that flow measurements are exactly what you want, however. > There are probably other ways to get the information you want (you haven't > gone into any detail). flow data is *very* expensive to process, summarize, > and store...or at least it can be depending on your application. True, if you're only interested in bytes-per-ip-address, that can be done using ipfw and a perl script invoked by cron to extract the counts, provided everything you need to track flows through one (or one of a set of) freebsd box(es). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message