From: Glen Turner <gdt@gdt.id.au>
To: "Flávio Pires" <flavio.defreitas@gmail.com>
Cc: netdev@vger.kernel.org, bridge@osdl.org
Subject: Re: Packet per Second
Date: Sat, 15 Dec 2007 09:01:53 +1030 [thread overview]
Message-ID: <1197671513.5973.10.camel@andromache> (raw)
In-Reply-To: <nemoFri121407105527@flis.man.torun.pl>
On Fri, 2007-12-14 at 15:34 +0000, Flávio Pires wrote:
> Well, I work on an ISP and we have a linux box acting as a
> bridge+firewall. With this bridge+firewall we control the packet rate
> per second from each client and from our repeaters. But I can`t
> measure the packet rate per IP. Is there any tool for this?
The usual approach is to generate NetFlow records -- there are
a number of Linux tools for this. Collect them with a collector
(flow-tools being a common choice). Then have a Perl script
which reads the flow records, processes them whichever way you
desire, and drops the result into a rrdtool file (there are modules
for both reading the flow-tools data and outputing in the rrdtool
format). The rrdtool utilities have a limited range of graphs,
but there is a huge selection of graphing packages from other
authors for rrdtool-stored data (Drraw, etc). Flow-tools also
has some third-party analysis tools, some of those have good
"top talker" statistics.
This is a lot of work, since you are really putting a complete
measurement infrastructure in place to get the one statistic
you desire. But I'd encourage you to do that, since knowing
one statistic usually leads to further questions of the data.
--
Glen Turner, Senior Network Engineer
Australia's Academic & Research Network www.aarnet.edu.au
next prev parent reply other threads:[~2007-12-14 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 15:34 Packet per Second Flávio Pires
2007-12-14 16:56 ` [Bridge] " Stephen Hemminger
2007-12-14 17:30 ` Flávio Pires
2007-12-14 22:31 ` Glen Turner [this message]
2007-12-17 11:18 ` Flávio Pires
2007-12-17 12:22 ` Matti Aarnio
2007-12-18 0:26 ` Glen Turner
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=1197671513.5973.10.camel@andromache \
--to=gdt@gdt.id.au \
--cc=bridge@osdl.org \
--cc=flavio.defreitas@gmail.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).