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] Multiple classes
Date: Tue, 03 Dec 2002 21:03:39 +0000	[thread overview]
Message-ID: <marc-lartc-103895610805858@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103889506715109@msgid-missing>

On Tuesday 03 December 2002 18:39, Homer Parker wrote:
> On Tue, 3 Dec 2002 11:29:00 +0100 Stef Coene <stef.coene@docum.org>
> wrote....
>
> > > different things, all failing, some worse than others. The end result
> > > is to throttle back 126 IP's individually. I've read so much over the
> > > last few days, I've almost confused myself, and probably have ;)
> > > Thanks for any and all help!
> > >
> > > tc qdisc add dev $DEV0 root handle 1: htb default 20
> > >
> > > tc class add dev $DEV0 parent 1: classid 1:1 htb rate 128kbit \
> > >   burst 6k
> > >
> > > tc class add dev $DEV0 parent 1:1 classid 2: htb rate 128kbit \
> > >   burst 6k
> >
> > All class attached to the same qdisc have the same major number.
> > Numbering of classes and qdiscs : <major nuber>:<minor numer>.
> > 2: is a valid name for a qdisc, but not for a class.
>
> 	Ok, I've tried grasping what you are telling me here, let's see how far
> off I am now... From the example in 9.5.5.1:
>
> # tc qdisc add dev eth0 root handle 1: htb default 30
>
> # tc class add dev eth0 parent 1: classid 1:1 htb rate 6mbit burst 15k
>
> # tc class add dev eth0 parent 1:1 classid 1:10 htb rate 5mbit burst 15k
> # tc class add dev eth0 parent 1:1 classid 1:20 htb rate 3mbit ceil 6mbit
> # burst 15k tc class add dev eth0 parent 1:1 classid 1:30 htb rate 1kbit
> # ceil 6mbit burst 15k
>
> The author then recommends SFQ for beneath these classes:
>
> # tc qdisc add dev eth0 parent 1:10 handle 10: sfq perturb 10
> # tc qdisc add dev eth0 parent 1:20 handle 20: sfq perturb 10
> # tc qdisc add dev eth0 parent 1:30 handle 30: sfq perturb 10
>
> Add the filters which direct traffic to the right classes:
>
> # U32="tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32"
> # $U32 match ip dport 80 0xffff flowid 1:10
> # $U32 match ip sport 25 0xffff flowid 1:20
>
> 	If I started with something similar to this, then I would just start
> building under the 10:, 20:, 30: for the different IP's? If that's the
> case, then I would send all of x.x.x.x to 10:1, and then have the
> different rates and priorities within th 10:1 block? Am I on the right
> track, or completely out in left field?
It all depends on what you want to do.  Have you read my docs on www.docum.org 
??  But you are on the right track.
I have some remarks.  1kbit rate is _very_ low.  And 15k burst is not much for 
5mbit rate.  If you don't specify the burst or cburst paramter, tc will 
calculate the most optimal setting for you.

> >      #lartc @ irc.oftc.net
> 	I can never find anyone in there, lots of names, no responses :(
I'm there if I'm at home (nick name staf).

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:[~2002-12-03 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03  5:49 [LARTC] Multiple classes Homer Parker
2002-12-03 10:29 ` Stef Coene
2002-12-03 17:39 ` Homer Parker
2002-12-03 21:03 ` Stef Coene [this message]
2002-12-04 10:08 ` Homer Parker

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-103895610805858@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