[LARTC] can't understand howto example

[LARTC] can't understand howto example

[Hariett Jones]

tc class add dev $DEV parent 1: classid 1:1 htb rate ${UPLINK}kbit burst 6k

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

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 ?

copied from : http://lartc.org/howto/lartc.cookbook.ultimate-tc.html#AEN2241



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

Re: [LARTC] can't understand howto example

[Stef Coene]

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/