Thank you Paolo for the fast and detailed answer,
> Alternatively, you might still want to go with your original setup
> (sum_host) introducing the networks_file directive (see CONFIG-KEYS
> for further infos) in your config, ie.
>
> networks_file: /path/to/networks.lst
>
> and inside your networks.lst file, just one line:
>
> 192.168.0.0/16
If i use sum_host with networks.lst containing 192.168.0.0/16, is it
right, that only traffic inside 192.168.x.x will be accounted?
For example
only inside the local network?
192.168.0.1 <--> ..... <--> 192.168.0.11
or also for the connection from/to local network?
192.168.0.1 <--> ..... <--> 217.237.149.161
If i understand you correctly, the traffic for the second example will
be rewritten as 0.0.0.0, isn't it?
> Such setup will allow you to get two different SQL tables: acct_in
> containing incoming traffic to your 192.168.x hosts and acct_out
> containing outgoing traffic from your 192.168.x hosts on a per-host
> basis. On a plus side, your tables will remain small. You can also
> still choose dynamic tables on top of this.
Accounting by "aggregate: ip_src,ip_dst" gives me also the In- and
Outcoming Traffic for each local client?
What is the difference between using the aggregate_filter directive and
the normal aggregate directive?
Thanks for your answer,
Mirko
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
