From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Monitoring problem,
Date: Thu, 24 Apr 2003 19:15:27 +0000 [thread overview]
Message-ID: <marc-lartc-105121181712177@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105099580521956@msgid-missing>
On Thursday 24 April 2003 07:56, hare ram wrote:
> Hi
>
> thanks, for the quick reply
>
> I have made configuration like
> each block like x.x.x.0/24 should get 128kbps
> another Block y.y.y.0/24 should get 256kbps
>
> when when i mark them and divert to IMQ Device
>
> iam not able to achive this, iam able to control only uploads
>
> but downloads iam able to see maximum ceil of b/w
>
> would mind give me small example where i can control both sides
No, because I don't have one.
> and another question is, i have created the rules more than 2 class
> But iam not able to see more than 2 class, when i do monitor_tc.pl
monitor_tc.pl uses the output of
tc -s -d class show dev eth0
It works fine for me. What do you see when you execute that command? Do you
see all classes? Maybe my script can't handle the fact that you add a htb
qdisc to a htb class.
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:[~2003-04-24 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 7:37 [LARTC] Monitoring problem, hare ram
2003-04-23 5:29 ` hare ram
2003-04-23 20:06 ` Stef Coene
2003-04-24 5:47 ` hare ram
2003-04-24 19:15 ` 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-105121181712177@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 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.