From: Michael Eck <michael.eck@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc+mrtg
Date: Thu, 19 Aug 2004 15:15:41 +0000 [thread overview]
Message-ID: <d82fbdb7040819081536e06da4@mail.gmail.com> (raw)
In-Reply-To: <014901c46d7d$0e58d9a0$15a02bca@gsd03>
I can't seem to find tcrrd2.pl on the site.
On Fri, 23 Jul 2004 19:45:51 +0200, Stef Coene <stef.coene@docum.org> wrote:
> On Tuesday 20 July 2004 07:43, Kristiadi Himawan wrote:
> > I already use external script that fetch iptables mangle table from
> > PREROUTING and POSTROUTING counter.
> > But the traffic isn't really accurate, i found when there's bulk UDP
> > traffic come to the shaper, my mrtg shown that
> > the traffic shown bigger than allocated bandwidth for that class. So the
> > question, it's possible to make script from tc command,
> > that count bandwith acctually passing through the shaper.
> You can patch snmp so you can get the tc counters and process them in a custom
> script or use mrtg:
> http://www.docum.org/docum.org/tc-snmp/
>
> Stef
>
> --
> stef.coene@docum.org
> "Using Linux as bandwidth manager"
> http://www.docum.org/
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-08-19 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 10:42 [LARTC] tc+mrtg Kristiadi Himawan
2004-07-19 12:20 ` Roy
2004-07-19 13:00 ` Gideon le Grange
2004-07-19 13:47 ` Rene Gallati
2004-07-19 16:20 ` Alessandro Ren
2004-07-20 1:42 ` Rio Martin.
2004-07-20 5:43 ` Kristiadi Himawan
2004-07-23 17:45 ` Stef Coene
2004-08-19 15:15 ` Michael Eck [this message]
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=d82fbdb7040819081536e06da4@mail.gmail.com \
--to=michael.eck@gmail.com \
--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.