All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Gale <michael@bluesuperman.com>
To: netfilter@lists.netfilter.org
Subject: Re: Performance Monitoring
Date: Mon, 5 Jan 2004 23:01:15 -0700	[thread overview]
Message-ID: <20040105230115.687bded9.michael@bluesuperman.com> (raw)
In-Reply-To: <20040106033802.30955.qmail@paus.pesat.net.id>

Hello,

	Yesterday I was a reply on Performance Monitoring on the netfilter mail
list, it suggested the user use IPAC-NG. The admin then have to create a
chain for each IP they want to monitor.

I did not think this is a good idea ... so for those of you who want to
do bandwidth monitoring I suggest you check out the following. Here is a
list of ones I have tried.

ntop -- provides a web GUI for real time monitoring. Using it now on a
firewall box to monitoring traffic on each interface. 

Adv .. provides great states , very detailed
Dis .. seems to be some over header ... uses a DDR db :(

You can use curl to pull the stats nightly and save them to a text file.
Then create a little PHP scritp to provide you with the numbers. Now you
will have stats for as long as you want.

iptraf -- not bad ... detail is low.

Adv ... NO over head and works great on a work station or 1 interface
machine. It takes a bit to setup because you have to create all the
filters your self.

Dis ... out is simple ... a php script to produce a nice web GUI is
needed.

Nagios -- http://www.nagios.org/
	Could be over kill depending on what you want ... this is more of a
network monitoring tool. Really not designed to be run with one machine
in mind.

IPFM -- not bad .. very simple:

example:
HOST                          IN         OUT       TOTAL
host1.domain.com           12345     6666684     6679029

MRTG for total traffic accounts only

Bandwidthd -- not bad ... currently testing it. Seems to provide web png
files much like MRTG but does provide host info. I do not believe you
are able to save the data though :(


Michael.


On Tue, 06 Jan 2004 10:38:02 +0700
"bino" <bino@indoakses-online.com> wrote:

> I my self don't familiar with IPAC-NG.
> The basic logic block is :
> 1. use the feature of iptables -N to create per ip-addr IN and Out
> chain 2. jump every traffic per ip addr, to respective chain 
> 
> use cron to run the bash-script that do :
> 1. iptables -L -vnx
> 2. Parse the data from each respective chain
> 3. stor it to remote MySQL using MySql client tool
> 4. reset (zero ?) the value of each chain 
> 
> That way you can have a traffic record per station (ip addr) 
> 
> If you just need monitoring like MRTG (in bps, no detailed history
> record), it'll more simple ... you only need to hack NetSNMPD and use
> MRTG to do the rest, no SQL hasle. 
> 
> Sincerely
>  -bino- 
> 
> Alex Satrapa writes: 
> 
> > Lawrence Tang wrote:
> >> Does this will help to calculate each PC on LAN MB usage report ??
> > 
> > You should be able to configure it to do so. IPAC-NG uses separate 
> > accounting rules for every item that you want to report on. Thus if
> > you want individual accounting per PC, you can set it up to do so. 
> > 
> > Install it and fiddle. That's my recommendation. 
> > 
> > Alex Satrapa 
> > 
> >  
> > 
> > 
>  
> 
> 


-- 
Hand over the Slackware CD's and back AWAY from the computer, your geek
rights have been revoked !!!

Michael Gale
Slackware user :)
Bluesuperman.com 


  parent reply	other threads:[~2004-01-06  6:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 22:03 Performance Monitoring Barry Rooney
2004-01-05 22:27 ` Alex Satrapa
2004-01-06  1:57   ` Lawrence Tang
2004-01-06  4:04     ` Alex Satrapa
2004-01-06  3:38       ` bino
2004-01-06  5:58         ` Michael Gale
2004-01-06  6:01         ` Michael Gale [this message]
2004-01-06  6:02         ` Michael Gale
2004-01-10  0:04           ` Ramin Dousti
2004-01-10  8:54             ` Thhoep
2004-01-11 23:26             ` Alex Satrapa
2004-01-11 23:32               ` Antony Stone

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040105230115.687bded9.michael@bluesuperman.com \
    --to=michael@bluesuperman.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.