[ previous ] [ next ] [ threads ]
 
 From:  "John Voigt" <1geek at jvoigt dot com>
 Cc:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall] RE: monitoring traffic per IP
 Date:  Fri, 16 Jan 2004 15:11:42 -0500
This is not monowall (it's a very hacked monobsd actually) but it could be
easily added:

http://mrtg.reston-wireless.net/

Note that the actual graphs and mrtg stuff is done on the same machine that
the Soekris/monobsd box is sending syslogs to and not locally where the IP
addresses are actually located.  Most of those address have not yet been
assigned so only the ones at the end have any data.

A php program is executed by mrtg that connects to a web server on the
Soekris which executes a cgi shell script to return the raw data for the IP
addresses.  Since there is already a webserver and php on monowall, all that
is needed is a simple script to return data to the remote collector.

Here's what I use:

#!/bin/sh
echo Content-type: text/html
echo
echo ""
echo `uptime`
if [ $# = 0 ]
then
        /sbin/ipfw show
else
        /sbin/ipfw show | grep $1
fi
echo ""

Note that you need IPFW rules for each IP in each direction.  Here's a
sample:

#pipes for ip 38.119.96.126
pipe 12601 config bw 64K
pipe 12602 config bw 512K
#Use above pipes to limit address 38.119.96.126
add 12611 pipe 12601 ip from 38.119.96.126 to any
add 12612 pipe 12602 ip from any to 38.119.96.126

The pipes limits upstream bandwidth to 64k and downstream to 512k and the
rules push the data through the pipes and also force ipfw to do accounting.

Is that anything like what you were looking for?

John/

John Voigt, President

Reston Wireless, LLC
High speed internet service
no smoke, no mirrors, no wires (tm)
http://www.reston-wireless.net/

----- Original Message ----- 
From: "Honson, Steven N" <steven dot honson at education dot tas dot gov dot au>
To: "Martin Holst" <mail at martinh dot dk>; "Michal Cech" <cech at finalnet dot cz>
Cc: <m0n0wall at lists dot m0n0 dot ch>
Sent: Thursday, January 15, 2004 9:09 PM
Subject: RE: [m0n0wall] RE: monitoring traffic per IP


Another option could be IPFM with something like SCR_IPFM as the front
end...

http://robert.cheramy.net/ipfm/
http://scripfm.sourceforge.net/

Cheers,
Steven

-----Original Message-----
From: Martin Holst [mailto:mail at martinh dot dk]
Sent: Friday, 16 January 2004 12:08 PM
To: 'Michal Cech'
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: [m0n0wall] RE: monitoring traffic per IP

Hi Michal!

Sorry for not answering your first post about the subject.
It has however been discussed before.
MIBs for IP-accounting is not implemented in m0n0walls SNMP-agent
(AFAIK).

If you are looking for IP-accounting for m0n0wall, I suggest you support
Roberto Zilli's IP traffic daemon by letting him know your opinion.
It seems like a promising project.

See this post:
http://m0n0.ch/wall/list/?action=show_msg&actionargs[]=23&actionargs[]=2
9

/Martin

-----Original Message-----
From: Michal Cech [mailto:cech at finalnet dot cz]
Sent: 15. januar 2004 23:34
To: m0n0wall at lists dot m0n0 dot ch
Subject: [m0n0wall] monitoring traffic per IP

Please help.
How use SNMP (mrtg on server)  for read traffic per IP  (per client)
from
IPF or IPFW on monowall ?

(I find info:   UCD-SNMP: 4.2.6   support  IPFW (ucd-ipfwacc-mib))

Thanks for all
Michal


---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch



---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch




---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch