All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] dont get prios
Date: Fri, 03 Jan 2003 19:32:03 +0000	[thread overview]
Message-ID: <marc-lartc-104162252527259@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104162205026576@msgid-missing>

Esteban,

You will want to learn about "tc filter".  This is the method you use to
classify traffic.

Read about "tc filter" at lartc.org.

  http://lartc.org/howto/lartc.qdisc.filters.html

Try this first:

  http://lartc.org/howto/lartc.qdisc.filters.html#LARTC.FILTERING.SIMPLE

And if you want to try something fancy:

  http://lartc.org/howto/lartc.adv-filter.html

-Martin

 : im trying to understan qdisc && classes..i founded this example in
 : docum.org..
 :
 : some things i dont get..how do i say wich kind of traffic goes to
 : classid 1:10/1:11/1:12 ? based on what? ip? tos? what?
 :
 : tc qdisc add $DEV root handle 1: htb default 10
 : tc class add dev eth0 parent 1: classid 1:1 htb rate 100kbps ceil
 : 100kbps burst 2k
 : tc class add dev eth0 parent 1:1 classid 1:10 htb rate 30kbps ceil
 : 100kbps burst 2k prio 0
 : tc class add dev eth0 parent 1:1 classid 1:11 htb rate 10kbps ceil
 : 100kbps burst 2k prio 1
 : tc class add dev eth0 parent 1:1 classid 1:12 htb rate 60kbps ceil
 : 100kbps burst 2k
 :
 : thanks in advance
 : Esteban.
 :
 : _______________________________________________
 : LARTC mailing list / LARTC@mailman.ds9a.nl
 : http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
 :

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2003-01-03 19:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 19:27 [LARTC] dont get prios Esteban Ribicic
2003-01-03 19:32 ` Martin A. Brown [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-104162252527259@msgid-missing \
    --to=mabrown-lartc@securepipe.com \
    --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.