From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] is there an error here ?
Date: Mon, 13 Jan 2003 21:41:32 +0000 [thread overview]
Message-ID: <marc-lartc-104249426709095@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104246668627978@msgid-missing>
On Monday 13 January 2003 15:06, Rohit Talukdar wrote:
> 1. am a newbie in traffic shaping .
> was going thru http://www.docum.org/stef.coene/qos/faq/#2
> Under the para titled
> "Basic rules for traffic shaping with HTB"
>
> there is this line that reads:
> So 10, 200 and 300 are leaf classes = they have no child classes. And class
> 1 has a maximum of 100 due to the link limitation. So it really can't use
> more then 100.
>
> pardon me if i am wrong, but shouldnt (after looking at the figure)
> 20, 200 and 300 be the leaf classes instead of 10, 200 and 300.
> ( really apreciate the yeoman service rendered by stef coene in
> enlightening newbies like me)
Yep. Corrected.
> 2. also,
> [root@xyz root]# ip link list
> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc cbq qlen 100
> link/ether 00:80:ad:77:6b:46 brd ff:ff:ff:ff:ff:ff
> [root@xyz root]# ip rule list
> 0: from all lookup local
> 32766: from all lookup main
> 32767: from all lookup 253
>
> after adding the rules (using tc), what command should i use the list all
> the rules
tc -s -d class show dev eth0
tc -s -d filter show dev eth0
tc -s -d qdisc show dev eth0
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-01-13 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 14:18 [LARTC] is there an error here ? Rohit Talukdar
2003-01-13 21:41 ` 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-104249426709095@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