[ previous ] [ next ] [ threads ]
 From:  Justin Ellison <justin at techadvise dot com>
 Cc:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  RE: [m0n0wall-dev] Replacement for CPU/Memory graph
 Date:  Tue, 18 Oct 2005 11:33:13 -0500
On Tue, 2005-10-18 at 12:12 -0400, John Stoffel wrote:
>  - full SNMP support, with TRAPS.  This is key to me.
>  - the Memory/CPU graph could be in something less dynamic which is
>    more widely supported in browsers. 

As a "techie", I use both the SVG graph and the SNMP interfaces.  Tools
like MRTG/Cacti/etc by default poll every 5-15 minutes.  This gives you
a good average, but the SVG graph utility polls the info once every
second.  This really helps a person find out if their traffic is

I don't see where there needs to be any change.  The SVG utility doesn't
eat up much space at all, and only consumes resources if someone is
actually using it.  If you want SNMP polling, just set up SNMP and don't
use the SVG graph; if you want the SVG, don't turn on SNMP.

SNMP traps wouldn't be too hard to implement.  I did some tinkering with
the SNMPd that comes with m0n0 (UCD-SNMP not Net-SNMP) awhile ago.  The
main problem with it is that the binary used for m0n0 is tremendously
stripped down.  Adding just a couple of the more advanced features
quickly triples the size of the binary.  That being said, issuing a
'snmpd -H' from exec.php looks like the binary included does support
traps.  What traps are you needing sent?