Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] API using cbq / tc ?
Date: Sat, 08 Feb 2003 10:39:34 +0000	[thread overview]
Message-ID: <marc-lartc-104470084709816@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104453716713244@msgid-missing>

On Saturday 08 February 2003 08:02, Ming-Ching Tiew wrote:
> I am just written ( I won't say completed !) a
> program which performs traffic read operation.
> It is a VB client program talking to a C TCP
> socket server. Everything is based on scripting,
> so it could be flaky right now, so you might
> have to be patient :-) The server has been tested
> running on my Linux 2.4.20 machine.
>
> The VB GUI program charts the traffic data on per
> interface and per-class/qdisc basis. It also
> displays the class/qdisc relationship in a
> hierarchical (GUI) tree diagram. The intention is
> for you to determine how effective is your
> class/qdisc.
>
> The server is pure C ( without any other fancy
> libraries ) to reduce the footprint because my
> intention is to let it run on a floppy-based
> NAT firewall/router, which I have tested against
> floppyfw ( http://www.zelow.no/floppyfw/ ).
>
> I will be enhancing it in the future to allow
> service-by-service traffic charting, based on
> iptables' traffic counter.
>
> Any interest parties could mail to me and we shall
> see how thing goes.
I found this :
http://www.hav.com/java/scroll/
It's in java.  I tested it with some browsers and platforms and it works 
great.  The java class is not so difficult.  I contacted the original author 
for permission to use his java class, but I didn't received an answer.
I used his java class and made my own version so I could display class and 
qdiscs stats.  It works great.  But I can't publish it as long as I don't 
know if I may use it.
The data is delivered with a cgi-bin prog so you don't need an extra daemon.  
And the java class is cross-platform so you can see it in allmost any 
web-browser that supports java.

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/

  parent reply	other threads:[~2003-02-08 10:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 13:20 [LARTC] API using cbq / tc ? Srikanth
2003-02-07  2:28 ` S Mohan
2003-02-07  4:37 ` Srikanth
2003-02-07  7:44 ` Stef Coene
2003-02-08  7:02 ` Ming-Ching Tiew
2003-02-08 10:39 ` Stef Coene [this message]
2003-02-08 13:04 ` Ming-Ching Tiew
2003-02-08 13:22 ` Stef Coene
2003-02-09  3:45 ` Ming-Ching Tiew
2003-02-09  7:26 ` Henry Yen
2003-02-09 13:39 ` Stef Coene
2003-02-10  1:58 ` mingching.tiew
2003-02-10  8:59 ` Stef Coene
2003-02-10 18:01 ` Jay Wineinger
2003-02-10 18:20 ` Stef Coene
2003-02-11 16:59 ` Martin Devera
2003-02-11 18:16 ` Stef Coene
2003-02-12  8:29 ` devik
2003-02-12 17:45 ` Stef Coene
2003-02-13  8:30 ` devik
2003-02-13 10:36 ` mingching.tiew
2003-02-13 18:39 ` Stef Coene
2003-02-13 18:40 ` Stef Coene
2003-02-14  3:58 ` mingching.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-104470084709816@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