Hello, Even if you have a script that creates the chains for each IP .. if you use all the IP's from .1 to .250. Then a packet will have to be compared to 249 chains before if matches a chain if it is from or to IP .250. This is not good. Michael. On Tue, 06 Jan 2004 10:38:02 +0700 "bino" <bino@xxxxxxxxxxxxxxxxxxxx> 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
