diff --git a/docs/Accounting.xml b/docs/Accounting.xml index a45672c00..c3632dc9e 100644 --- a/docs/Accounting.xml +++ b/docs/Accounting.xml @@ -299,7 +299,7 @@ shorewall restart. This has a downside, however. If you change the network associated with an accounting table, then you must shorewall stop; shorewall start to have a successful - restart (counters will be cleared). + restart (counters will be cleared). Example: Suppose your WAN interface is eth0 and your LAN interface is eth1 with network 172.20.1.0/24. To account for all traffic between the @@ -321,6 +321,10 @@ ACCOUNT(net-loc,172.20.1.0/24) - eth1 eth0For each local IP address with non-zero counters, the packet and byte count for both incoming traffic (IP is DST) and outgoing traffic (IP is SRC) are listed. The -f option causes the table to be flushed (reset - all counters to zero) after printing. + all counters to zero) after printing. + + For a command synopsis: + + iptaccount --help diff --git a/manpages/shorewall-accounting.xml b/manpages/shorewall-accounting.xml index d0bcdba5f..8783bb422 100644 --- a/manpages/shorewall-accounting.xml +++ b/manpages/shorewall-accounting.xml @@ -117,9 +117,15 @@ (counters will be cleared). The counters in a table are - printed using the iptaccount utility. As of - February 2011, the ACCOUNT Target capability and the - iptaccount utility are only available when iptaccount utility. For a + command synopsis, type: + + + iptaccount --help + + + As of February 2011, the ACCOUNT Target capability and + the iptaccount utility are only available when xtables-addons is installed. See http://www.shorewall.net/Accounting.html#perIP