From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ipac/iptables + mrtg accounting
Date: Sun, 03 Nov 2002 14:50:02 +0000 [thread overview]
Message-ID: <marc-lartc-103633510008933@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103609888214381@msgid-missing>
On Sunday 03 November 2002 15:05, Pedro Larroy wrote:
> On Fri, Nov 01, 2002 at 09:56:36AM +0100, Stef Coene wrote:
> > On Friday 01 November 2002 03:06, Kenneth Porter wrote:
> > > --On Thursday, October 31, 2002 9:13 PM +0000 lartc@cnicules.4email.net
> > >
> > > wrote:
> > > > i've installed mrtg to make graphics of the trafic from the interfece
> > > > throw the snmpd, and the same with ipac witch put iptables accounting
> > > > rules colect them and store, and gets the output,
> > >
> > > Do you have a pointer to where to set up MRTG to do this? I couldn't
> > > find anything in the LARTC document about "measuring" or "snmp".
> >
> > Mrtg monitors only incoming and outgoing packets/bytes of a network
> > interface. I created my own script that uses the tc counter to create
> > some graphs. It look ugly, but I'm working on it. You can find it on
> > www.docum.org under GUI.
>
> I have some perl scripts for measuring with rrdtool.
>
> > I'm also trying to write a perl script that can extend the snmpd daemon
> > so you can also querying tc counters with snmp. But that script is not
> > working.
>
> How are you planning to integrate snmp with tc? Maybe we could gather
> the data at a lower layer rather than the output of tc.
I have a script that you can put in the snmd.conf. It gives all counters on 1
line. It works, but there is a limit on how much data you can send if you
use snmp.
I created a second script so you can do this :
snmpwalk server public .1.3.6.1.4.1.2021.257
enterprises.ucdavis.257.0.0 = "Network interface names"
enterprises.ucdavis.257.0.1 = "lo"
enterprises.ucdavis.257.0.2 = "eth0"
enterprises.ucdavis.257.1.0 = "Root classes"
enterprises.ucdavis.257.1.1 = ""
enterprises.ucdavis.257.1.2 = " 1:1 "
enterprises.ucdavis.257.2.2.1 = "Child information"
enterprises.ucdavis.257.3 = "CHILDS info of 1:"
Let's I want to know the child classes of 1:1
snmpwalk server public .1.3.6.1.4.1.2021.257.2.2.1.1
enterprises.ucdavis.257.2.2.1.2 = " 1:10 1:20 1:30 "
2.2.1.1 at the end means :
2 : device 2 = eth0
2 : give me the child onfi
1.1 : class 1:1
And so on. Each time you asks for something, a perl script is lanched, it
reads a config file so it knows the tc classes and childs. This config file
must exists and updated manually. It's ugly, but it works.
I have to find some info about snmp and even don't know if this script is
usefull. But you can have it if you want.
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/
prev parent reply other threads:[~2002-11-03 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 21:13 [LARTC] ipac/iptables + mrtg accounting lartc
2002-11-01 2:06 ` Kenneth Porter
2002-11-01 8:56 ` Stef Coene
2002-11-01 12:31 ` lartc
2002-11-01 12:35 ` lartc
2002-11-03 14:05 ` Pedro Larroy
2002-11-03 14:50 ` Stef Coene [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=marc-lartc-103633510008933@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