IP traffic accounting

In Linux, IP traffic can be counted using accounting rules, defined by the same characteristics as the firewall rules. Accounting is done at two places: when a packet is received and when a packet is sent out (see figure 3).

Figure 3

So, a packet being forwarded is counted twice: the first time just after its arrival, the second time when it is being sent out again. There is one single list of accounting rules, that is being used for both incoming and outgoing traffic. For every packet, all rules in this list are checked and the packet and byte counters of every matching rule are incremented. Note the difference with the firewall lists: scanning a list there stops at the first match.

The following ipfwadm command counts all http traffic related to people using your WWW-server from the outside:

   ipfwadm -A -a -b -W eth1 -P tcp -S 0.0.0.0/0 \
           -D 192.168.37.1 www

Here it is assumed that the local system, hosting the WWW-server, has IP address 192.168.37.1. We see some new options in this command. The -b option means ``bidirectional'', and makes that also packets coming from 192.168.37.1 (port 80) are counted. The -W option has an interface name as parameter, so that only traffic via that particular interface is taken into account. Packets passing another interface (e.g., an interface eth0 connected to your internal network) are not counted here.

Some suggestions to use accounting most effectively:

• Reset the counters at certain intervals via cron, for example every day or every hour. Currently, the counters are 32-bits unsigned integers, so they will wrap around after 4 GByte.
• Combining the -l (list) and -z (reset to 0) options will reset the counters immediately after showing their current values, so no packets will be left uncounted.
• The most extensive output you get with the -Alex set of options, optionally with -z (reset values) or -n (numeric output) added.
• If you want to count all traffic excluding some specific protocols, like http and ftp, you can define rules for counting all traffic and rules for counting those protocols. Then just subtract the values from each other.

When listing the accounting rules (and the associated values) with ipfwadm, the pseudo-file /proc/net/ip_acct is read.

ÿÿÿ