[ previous ] [ next ] [ threads ]
 From:  "Joe Marr" <joemarr at suscom dot net>
 To:  "'Bruce A. Mah'" <bmah at acm dot org>, "'Josh Davis-Ryan'" <joshdr77 at hotmail dot com>
 Cc:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] feature request and a bug
 Date:  Tue, 11 Nov 2003 12:14:23 -0500
What about opening the snmp entity up so that we can pull more the interface
stats? Id like to know things like CPU and memory usage.

I agree that the stats function should be bare minimal on the box its self,
but getting some oids for mem and cpu would be great.

-----Original Message-----
From: Bruce A. Mah [mailto:bmah at acm dot org] 
Sent: Tuesday, November 11, 2003 11:26 AM
To: Josh Davis-Ryan
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] feature request and a bug

If memory serves me right, Josh Davis-Ryan wrote:

> feature request:
> *a page which displays total weekly, monthly bandwidth usage - as many ppl

> have capped internet.

I bet you could do this pretty easily with some sort of SNMP
accounting package.  m0n0wall can make its interface byte- and
packet-counters available via SNMP...I have MRTG set up to get
statistics in this way.  (MRTG doesn't do exactly what you want but
you get the idea.)

I'd recommend that you store the traffic statistics on some other
device, rather than trying to incorporate this into m0n0wall itself,
because m0n0wall wasn't really designed for keeping persistant storage
(also, keeping it small and non-bloated is kind of important for a
fair number of users).

Good luck!