Re: [LARTC] Wondershaper working, but not quite as expected

[Trevor Warren <trevorwarren@softhome.net>]

Michael,

 Maybe we can help you out much better if you could space out the
sentences below. They seem to be a jigsaw puzzle.

Trevor


On Sat, 2003-07-12 at 20:12, Michael Frotscher wrote:
> Hello, LARTC-List
> 
> I try to get my traffic-shaping done with Wondershaper 1.1a. When I run
> the script, the verbose output looks good (using a SuSE-8.2-box with
> iproute2-2.4.7-473):
> 
> + DOWNLINK\x1800
> + UPLINK\x150
> + DEV=ppp0
> + NOPRIOHOSTSRC> + NOPRIOHOSTDST> + NOPRIOPORTSRC> + NOPRIOPORTDST> + '[' '' = status ']'
> + tc qdisc del dev ppp0 root
> + tc qdisc del dev ppp0 ingress
> + '[' '' = stop ']'
> + tc qdisc add dev ppp0 root handle 1: htb default 20
> + tc class add dev ppp0 parent 1: classid 1:1 htb rate 150kbit burst 6k
> + tc class add dev ppp0 parent 1:1 classid 1:10 htb rate 150kbit burst
> 6k prio 1+ tc class add dev ppp0 parent 1:1 classid 1:20 htb rate
> 135kbit burst 6k prio 2+ tc class add dev ppp0 parent 1:1 classid 1:30
> htb rate 120kbit burst 6k prio 2+ tc qdisc add dev ppp0 parent 1:10
> handle 10: sfq perturb 10+ tc qdisc add dev ppp0 parent 1:20 handle 20:
> sfq perturb 10+ tc qdisc add dev ppp0 parent 1:30 handle 30: sfq perturb
> 10+ tc filter add dev ppp0 parent 1:0 protocol ip prio 10 u32 match ip
> tos 0x10 0xff flowid 1:10+ tc filter add dev ppp0 parent 1:0 protocol ip
> prio 10 u32 match ip protocol 1 0xff flowid 1:10+ tc filter add dev ppp0
> parent 1: protocol ip prio 10 u32 match ip protocol 6 0xff match u8 0x05
> 0x0f at 0 match u16 0x0000 0xffc0 at 2 match u8 0x10 0xff at 33 flowid
> 1:10+ tc filter add dev ppp0 parent 1: protocol ip prio 18 u32 match ip
> dst 0.0.0.0/0 flowid 1:20+ tc qdisc add dev ppp0 handle ffff: ingress
> + tc filter add dev ppp0 parent ffff: protocol ip prio 50 u32 match ip
> src 0.0.0.0/0 police rate 1800kbit burst 10k drop flowid :1
> 
> My ADSL-Line performs 2MBit down and 192kbit upstream, so I guess the
> values are allright. I then start an upload and am pleased to see that
> the upload-rate stays at 150kBit, as set. Pings then are fine.
> 
> But that upload limit is somehow not really enforced. When starting a
> second upload, the total rate (checked with iptraf) exceeds the set
> 150kBit and is only restricted by the line limit - pings of well over
> 3 seconds are the result.
> 
> What did I do wrong here?
-- 
( >-        LINUX, It's all about CHOICE      -< )
/~\    __        twarren@redhat.com       __   /~\
|  \) /  Pre Sales Consultant - Red Hat     \ (/ |
|_|_  \    9820349221(M) | 22881326(O)      / _|_|
       \___________________________________/

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