From: Omry Yadan <omry_y@inter.net.il>
To: lartc@vger.kernel.org
Subject: [LARTC] Bandwidth monitoring tool
Date: Fri, 17 Jun 2005 06:00:34 +0000 [thread overview]
Message-ID: <42B26702.10802@inter.net.il> (raw)
Hi.
I am trying to shape my upstream bandwidth, mostly per port. and I am
having some problems getting things to work the way I want them to.
before I throw my configuration at you guys ;), I`d like to debug it by
myself - but I was not able to find a tool that allow me to
monitor current bandwidth usage per port (and preferably even per port+ip).
I want to know what is the current bandwidth passing through port 80
(all connections), and in port 80, I`d like to
know what is the badnwidth usage per IP (regardless of the number of
sockets that are opened from that IP).
anyone?
thanks.
Omry.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2005-06-17 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 6:00 Omry Yadan [this message]
2005-06-17 17:31 ` [LARTC] Bandwidth monitoring tool Nelson Castillo
-- strict thread matches above, loose matches on Subject: below --
2005-06-17 6:19 Andreas Unterkircher
2005-06-17 8:09 ` Andreas Unterkircher
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=42B26702.10802@inter.net.il \
--to=omry_y@inter.net.il \
--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.