In fact,instead of loggging each packet, you should simply use the 2 counters
associated with each rule. So, for example:
Chain FORWARD (policy ACCEPT 2408 packets, 1136110 bytes)
pkts bytes target prot opt in out source
destination
0 0 all -- * * 192.168.1.1
0.0.0.0/0
Then account on it. ip-ng does this parsing and store the counters.
Pay attention that thoses counters are 64bit ones and not 32 bit as usual.
On Fri, Mar 22, 2002 at 01:59:05PM +1100, [EMAIL PROTECTED] wrote:
> Hi to everybody on the list
>
> Thanks to all who replied to my Solaris / Linux query a couple of weeks
> ago.
>
> I need a little help with a iptables problem.
>
> I am trying to configure a linux machine to sit between two networks and
> log data downloads by hosts.
>
> ie 192.168.10.0 - - - - - - - - - - - --eth0 - linux box - eth1 - - - -
> - - - - - - - - - - - - - - - 192.168.20.0
>
> I can currently log traffic using iptables to all destinations on y.0 using
> a separate rule under OUTPUT
>
> -A FORWARD -j LOG --log-level 6 -d 192.168.2.0/255.255.255.0 -i eth1
> -A OUTPUT -j LOG --log-level 6 -d 192.168.20.8
> -A OUTPUT -j LOG --log-level 6 -d 192.168.20.9
> -A OUTPUT -j LOG --log-level 6 -d 192.168.20.10
>
> And these messages are being logged to a file.
>
> Does anyone have a suggestion for software that generates reports on the
> amount of data going to each server that I can use for billing on a monthly
> basis??
>
> regards
>
> Grant
>
>
> --
> SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
> More Info: http://lists.slug.org.au/listinfo/slug
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
