From: Rowan Reid <rreid@studio3arc.com>
To: 'dizma' <nick@riskeng.bg>, netfilter@lists.netfilter.org
Subject: RE: Measuring traffic
Date: Fri, 13 Sep 2002 10:05:10 -0700 [thread overview]
Message-ID: <002801c25b47$b8007ac0$6b01a8c0@s3ac> (raw)
In-Reply-To: <00bb01c25afc$80e56190$37d2a8c0@nikodimov>
Hi,
Thanks for the recommendation, Since you suggested I figured I would
ask. D you have a sampl ipac.conf file. The source file and compile
didn’t' create one and I'm having a hard time understanding the exaple
. See insert.
INSTALLATION / CONFIG FILE.
The ipac.conf file is '/etc/ipac-ng/ipac.conf'. ipac.conf controls what
data
is collected. Each line which begins with a '#' is ignored. All the
other lines have the format
Name of rule|direction|interface|protocol|source|destination
where
Name of rule Any string to identify this rule
direction 'in' or 'out'
interface ip number or interface name or empty
protocol 'tcp' or 'udp' or 'icmp' or 'all'
source \
destination both as described in ipfwadm(8), or empty
In the summaries, the 'Name of rule' string identifies the counter.
Both the source and destination must be in ipfwadm/ipchains syntax -
consult the man page.
The interface can be named (for example, eth0) or its IP number can be
given.
Linux IP accounting always counts at one interface or at any interface.
The
direction means in or out of this interface.
* You must run the fetchipac -S after changing the
* ipac.conf file every time for the changes to take effect!
An example ipac.conf file comes with the distribution.
Cant' find it anywhere in the source
> try ipac-ng packet
>
> http://sourceforge.net/projects/ipac-ng/
>
next prev parent reply other threads:[~2002-09-13 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 16:45 Measuring traffic Rowan Reid
2002-09-12 18:53 ` Antony Stone
2002-09-13 8:06 ` dizma
2002-09-13 17:05 ` Rowan Reid [this message]
2002-09-13 17:27 ` Rowan Reid
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002801c25b47$b8007ac0$6b01a8c0@s3ac' \
--to=rreid@studio3arc.com \
--cc=netfilter@lists.netfilter.org \
--cc=nick@riskeng.bg \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox