From: NightInTheCity@softhome.net
To: lartc@vger.kernel.org
Subject: Re: [LARTC] realtime trafic monitor
Date: Tue, 23 Nov 2004 00:27:43 +0000 [thread overview]
Message-ID: <621244206.20041123022743@softhome.net> (raw)
In-Reply-To: <000601c4d085$ec82a830$340aa8c0@unix>
hmmm ... i don't really know if i should classify this as
real time, but i'll go ahead.
depends how much of your real time are u going to spend on it.
background:
following multiple papers@web first i started parsing whetever tool's
output came in my hand e.g. ifconfig and so on, than i upgraded to
ipchains/later on iptables accounting. (e.g create 2 chains, jump dst /
src from ips to be monitored, querry the chain). still no
satisfaction. than iptraf and friends. [and i even parsed human
readable output to rrdtool's rrds.] still no satisfaction. this is not
realtime. (or realtime = very complex for me?)
following cisco's NetFlow implementations @ linux i came across
multiple tools that would do similar things to ip flow export in cisco
routers. none until couple of months guaranteed my satisfaction. i
mean softflowd (disliked promiscuous mode), fprobe/ulogd-probe (too
harsh combination of ulogd targets and network traffic sampling) and
so on. even ntop.
so i would recommend strongly using <<ipcad>> daemon to implement network
traffic sampling and NetFlow export; flow-tools to capture NetFlow
dataflow and analyze. and this is real time by all means traffic
monitoring.not just 100kbps on this target, but 10 packets there, 200
bits there, when, where, all beeing agregated and transformed to feed one's joy to
handle numbers. lots.
have phun.
NightInTheCity
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-11-23 0:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 11:25 [LARTC] realtime trafic monitor Gogu Ionut
2004-11-22 11:37 ` Rajkumar S
2004-11-22 11:45 ` Michael Schwartzkopff
2004-11-22 11:49 ` Gogu Ionut
2004-11-22 11:56 ` Michael Schwartzkopff
2004-11-22 12:41 ` Nachko Halachev
2004-11-22 13:08 ` Ronny Aasen
2004-11-23 0:27 ` NightInTheCity [this message]
2004-11-23 1:25 ` Josh Nerius
2004-11-25 2:06 ` micah milano
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=621244206.20041123022743@softhome.net \
--to=nightinthecity@softhome.net \
--cc=lartc@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.