|Newer page:||version 9||Last edited on Wednesday, September 17, 2003 6:55:22 pm||by CraigBox|
|Older page:||version 7||Last edited on Wednesday, September 17, 2003 2:39:54 pm||by CraigBox||Revert|
@@ -9,16 +9,15 @@
* only supports ipchains based kernels (it has a big brother for iptables called ipac-ng which is close enough)
Note: linux kernel 2.2 used ipchains, 2.4 uses iptables.
-HOW DOES IT WORK?
+ HOW DOES IT WORK?
ipac consists of two scripts (shell and perl) and one C program:
* ipacset reads a configuration file and sets up ip accounting for the kernel using ipfwadm or ipchains
-* fetchipac, executed from cron once in a while, reads the current ip accounting data assembled by the kernel
and writes it to a new file
+* fetchipac, executed from cron once in a while, reads the current ip accounting data assembled by the kernel and writes it to a new file
* ipacsum(8) summarizes the data from a set of files and, optionally, replaces these files by one. It displays the values as a simple table containing the sums, as png graph pictures or as ascii graph pictures.
@@ -27,9 +26,9 @@
If you're running debian, the config file format is slightly different to newer versions. You don't have ipac~in/out/fwin etc, you just have 'in' and 'out', and both in and out get called on the forward chain.
If you're running ipac on a machine that is a gateway between two networks, you will find that your totals are largely irrelevant because if I download 2Mb of stuff, I will get 2Mb in on the external interface and then 2Mb out on the internal interface.
-The easiest way around this is to simply monitor your
interface. You really don't care about internal traffic because it's all free.
+The easiest way around this is to simply monitor your interface. You really don't care about internal traffic because it's all free.
Edit /etc/ipac-ng/ipac.conf and replace the +'s with 'eth1' or 'ppp0' etc.