All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] can't understand howto example
Date: Thu, 21 Oct 2004 19:22:31 +0000	[thread overview]
Message-ID: <200410212122.31193.stef.coene@docum.org> (raw)
In-Reply-To: <41776403.9040504@wp.pl>

On Thursday 21 October 2004 09:23, Hariett Jones wrote:
> tc class add dev $DEV parent 1: classid 1:1 htb rate ${UPLINK}kbit burst 6k
This is for packets leaving device $DEV.

> tc qdisc add dev $DEV handle ffff: ingress
>
> tc filter add dev $DEV parent ffff: protocol ip prio 50 u32 match ip src \
>   0.0.0.0/0 police rate ${DOWNLINK}kbit burst 10k drop flowid :1
This is for packets entering device $DEV.  "flowid :1" is an other destination 
as "classid 1:1" in the previous line.  Read "flowid :1" as "flowid ffff:1".

> why does the download is being sent to class 1 which is limited by uplink ?
> why the rate is being mentioned in filter and in class ?
For ingress, the destination is not important.  It's the policer that counts 
and that limits the matching packets to a certain rate (${DOWNLINK}kbit in 
this example).

Stef

-- 
stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2004-10-21 19:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21  7:23 [LARTC] can't understand howto example Hariett Jones
2004-10-21 19:22 ` 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=200410212122.31193.stef.coene@docum.org \
    --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.