From: John Haxby <john.haxby@oracle.com>
To: Jeff Jensen <jjensen@unyalli.com>
Cc: netfilter@vger.kernel.org
Subject: Re: explanation of the syslog LEN and WINDOW entries
Date: Wed, 28 Oct 2009 15:35:25 +0000 [thread overview]
Message-ID: <4AE864BD.5080508@oracle.com> (raw)
In-Reply-To: <b376a78e0910280756h4ba10f1oea023c6b870fe0cb@mail.gmail.com>
On 28/10/09 14:56, Jeff Jensen wrote:
> The boss wants to know how much bandwidth is used by the different
> app's we allow. I have some unique app's that run on unique port(s)
> and rules that log all packets. I set the --log-prefix= to something
> unique to that app and every day sort it out into individual files. I
> was hoping to aggregate all the entries to a total bandwidth out and
> it.
>
I do this slightly differently. I collect information on a per-IP
address basis (this is all traffic flowing through a router) and within
each table I have rows that match a particular port/protocol and then
just -j RETURN.
Every hour I run "iptables -vxnL <table> -Z" for each table and then
merge the counters into a database. I have another process that
periodically looks at the database and produces pretty graphs of the
per-machine, per-protocol usage. (Well, actually, I haven't done
per-protocol yet, but I have the information needed.)
There's an accounting extension in xtables which would do the job
better, but I haven't attempted to persuade the xtables on CentOS 5 :-)
jch
next prev parent reply other threads:[~2009-10-28 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 13:53 explanation of the syslog LEN and WINDOW entries Jeff Jensen
[not found] ` <56378e320910280720q79cd3dma8eee31f3512a6c0@mail.gmail.com>
2009-10-28 14:56 ` Jeff Jensen
[not found] ` <56378e320910280811t48e13264nb8992e2be9492f1a@mail.gmail.com>
2009-10-28 15:21 ` Jeff Jensen
2009-10-28 15:35 ` John Haxby [this message]
2009-10-30 14:15 ` Jeff Jensen
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=4AE864BD.5080508@oracle.com \
--to=john.haxby@oracle.com \
--cc=jjensen@unyalli.com \
--cc=netfilter@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.