From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Monitoring....
Date: Thu, 13 Feb 2003 20:03:35 +0000 [thread overview]
Message-ID: <marc-lartc-104516961910697@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104515865524996@msgid-missing>
On Thursday 13 February 2003 20:35, Nelson Guedes Paulo Junior wrote:
> On Thu, 13 Feb 2003, Stef Coene wrote:
> > On Thursday 13 February 2003 18:49, Nelson Guedes Paulo Junior wrote:
> > > Hi all,
> > >
> > > Just shape my connection isn't enough. I need to monitoring what's
> > > happening, for example, I need to now if my users are downloading too
> > > much, if they are using too much ftp or if thei are ussing too much
> > > SSH. Other things that are relevant are Media Streaming, MP3
> > > Downloading and Web Traffic.
> > >
> > > BUT, some of these services negociate a high port and use these ports
> > > for the traffic. How do I prevent that to consume band and how do I log
> > > that and make graphics to justify and upgrade on my link
> > > infrastructure? How do I monitor this things???
> >
> > What if you monitor wel-known port (web, game ports, ...) and have an
> > other monitor for all the rest? And block all other ports so they have
> > to use the ports you monitor :)
> This is ok, but HOW I can do that??? (monitor, not block ok??)
You can use iptables. You can create a filter rule (or more) that matches the
packets you want to monitor. Schedule a iptables -L -v -n each 5 minutes and
use the byte counters to update a log file. I recommend rrdtool for it. I
have some scripts on www.docum.org. The monitor script uses the byte
counters of iptables to get some data. In the GUI section, you can find some
perl scripts that I use update the rrd files and to create the graph.
If you need more help, you can contact me. For the rrdtool, I recommend using
an existing script and adapt it to your needs so you don't have to bother
about the needed options.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-02-13 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 17:49 [LARTC] Monitoring Nelson Guedes Paulo Junior
2003-02-13 18:44 ` Stef Coene
2003-02-13 19:35 ` Nelson Guedes Paulo Junior
2003-02-13 20:03 ` Stef Coene [this message]
2003-02-13 21:37 ` Nelson Guedes Paulo Junior
2003-02-13 22:38 ` Stef Coene
2003-02-13 23:25 ` Ming-Ching Tiew
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=marc-lartc-104516961910697@msgid-missing \
--to=stef.coene@docum.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox