I do this using ipchains
I have yet to spend any time looking
at iptables but I guess that should
also work.
I setup my chains so that they are
effectively reports of throughput
my "input" chain on the internet
interface sends everything on to another
chain and the rule that does this is
effectively a total input byte counter
- though I do break it up into subnets
for my purposes -
(the next chain does the same again on
a per machine basis) then the next
chain handles the actual rules about
what is allowed in.
my output (based in the internet
interface) sends off to another chain
where the firewall rules decide what
is allowed out and goes onto another
chain ... then this does a per machine
rule on to the true output chain and
the true output chain is effectively
a byte count again of all output data
onto the internet
Each night I shutdown the link,
save the full dump of "ipchains -L -n -x -v"
and wipe and rebuild the chains so
the numbers are effectively zeroed
and bring the link up agian.
Thus I have a daily usage - my connection
is ADSL so the link going down and up
doesn't matter
I also use tcpdump to log every
packet that comes and goes but I
haven't looked around to see if there
are any good report tools for tcpdump
output.
Though every time I look through the
tcpdump logs I find port scans - sigh.
-Cheers
-Andrew Smith
>> -----Original Message-----
>> From: Christopher Scott Kindley [mailto:[EMAIL PROTECTED]]
>> Sent: July 18, 2001 11:58 AM
>> To: [EMAIL PROTECTED]
>> Subject: RE: Keeping track of downloaded data.
>>
>>
>> Would MRTG do the trick for you?
>>
>> http://people.ee.ethz.ch/~oetiker/webtools/mrtg/
>>
>
> Not really. I want to know how much data went through eth1 month by
> month. MRTG will only give me usage graphs over time, not totals.
>
> -Dan
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
