Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Jun 2002 08:29:35 -0400
From:      "Troy Settle" <troy@psknet.com>
To:        "'Wincent Colaiuta'" <wincentcolaiuta@mac.com>, <freebsd-isp@FreeBSD.ORG>
Cc:        "'Hans-Joachim Picht'" <hjp@lnxce.net>
Subject:   RE: Bandwidth billing and measurement scripts
Message-ID:  <001e01c21d0d$22715bf0$8a7c0440@psknet.com>
In-Reply-To: <1B02AF4B-8669-11D6-A31E-003065C60B4C@mac.com>

next in thread | previous in thread | raw e-mail | index | archive | help

Wincent,

Have you looked at cflowd for monitoring the flows through your router?

This can track by IP address and protocol.  There are some interesting
tools built around rrdtool that can generate some very nifty
graphs/reports.

Check it out, it's in the ports collection.

--
  Troy Settle
  Pulaski Networks
  540.994.4254 - 866.477.5638
  http://www.psknet.com
=20

> -----Original Message-----
> From: owner-freebsd-isp@FreeBSD.ORG=20
> [mailto:owner-freebsd-isp@FreeBSD.ORG] On Behalf Of Wincent Colaiuta
> Sent: Sunday, June 23, 2002 1:22 AM
> To: freebsd-isp@FreeBSD.ORG
> Cc: Hans-Joachim Picht
> Subject: Re: Bandwidth billing and measurement scripts
>=20
>=20
> El Sunday, 23 June, 2002, a las 04:45  AM, Hans-Joachim Picht=20
> escribi=F3:
>=20
> >> What I'd like it to do:
> >> - run as an hourly cron job
> >> - count incoming and outgoing bandwidth user per IP based on ipfw
> >> "count" rules - this should give a totally accurate traffic count
> >> without the need to resort to parsing mail, http and ftp=20
> logs (which
> >> could get very messy)
> >> - save ipfw output to disc for safe keeping
> >
> > A tool for that is already available. http://www.simon.org.ua/ipa/
>=20
> Thanks for the reply Hans. I had already checked out IPA and=20
> found that=20
> it wasn't quite what I was looking for. I had two main=20
> problems with it:=20
> firstly it was written in C, and I don't know C so I can't=20
> modify it or=20
> add to it to make it how I would like; and secondly, I'm not=20
> so sure I'm=20
> entirely happy with how deep it digs down into the kernel.=20
> From the IPA=20
> FAQ:
>=20
> > If you installed a new kernel or made some changes in the=20
> kernel, then=20
> > you should also rebuild ipa(8), becase it uses kernel=20
> structures and=20
> > they can be changed from one version of the operating=20
> system to another=20
> > one, but see below.
>=20
> Don't really feel like having to worry about my billing and invoicing=20
> system breaking down when I rebuild the kernel. That's why I want to=20
> stick with basic user-land accessible tools like Perl, sh and=20
> ipfw. In=20
> any case, I've done most of the scripting for my custom=20
> solution anyway=20
> now.
>=20
> Cheers
> Wincent
>=20
>=20
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-isp" in the body of the message
>=20
>=20


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001e01c21d0d$22715bf0$8a7c0440>