* [LARTC] Wondershaper working, but not quite as expected
@ 2003-07-12 14:42 Michael Frotscher
2003-07-13 4:53 ` Trevor Warren
2003-07-13 10:01 ` Michael Frotscher
0 siblings, 2 replies; 3+ messages in thread
From: Michael Frotscher @ 2003-07-12 14:42 UTC (permalink / raw)
To: lartc
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?
--
Cheers,
Michael aka. Tron
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [LARTC] Wondershaper working, but not quite as expected
2003-07-12 14:42 [LARTC] Wondershaper working, but not quite as expected Michael Frotscher
@ 2003-07-13 4:53 ` Trevor Warren
2003-07-13 10:01 ` Michael Frotscher
1 sibling, 0 replies; 3+ messages in thread
From: Trevor Warren @ 2003-07-13 4:53 UTC (permalink / raw)
To: lartc
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/
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [LARTC] Wondershaper working, but not quite as expected
2003-07-12 14:42 [LARTC] Wondershaper working, but not quite as expected Michael Frotscher
2003-07-13 4:53 ` Trevor Warren
@ 2003-07-13 10:01 ` Michael Frotscher
1 sibling, 0 replies; 3+ messages in thread
From: Michael Frotscher @ 2003-07-13 10:01 UTC (permalink / raw)
To: lartc
Hallo, Trevor
> Maybe we can help you out much better if you could space out the
> sentences below. They seem to be a jigsaw puzzle.
Sorry, you are right - I think my word-wrapping is messing this up. I'll
post it again, disregarding line lengths.
This is the verbose output when the script starts:
+ 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: cbq avpkt 1000 bandwidth 10mbit
+ tc class add dev ppp0 parent 1: classid 1:1 cbq rate 150kbit allot 1500 prio 5 bounded isolated
+ tc class add dev ppp0 parent 1:1 classid 1:10 cbq rate 150kbit allot 1600 prio 1 avpkt 1000
+ tc class add dev ppp0 parent 1:1 classid 1:20 cbq rate 135kbit allot 1600 prio 2 avpkt 1000
+ tc class add dev ppp0 parent 1:1 classid 1:30 cbq rate 120kbit allot 1600 prio 2 avpkt 1000
+ 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 11 u32 match ip protocol 1 0xff flowid 1:10
+ tc filter add dev ppp0 parent 1: protocol ip prio 12 u32 match ip protocol 6 0xff match u8 0x05 0x0f at 0 match u16 0x0000 0xffc0 at 2 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
This is the status information while running:
+ DOWNLINK\x1800
+ UPLINK\x150
+ DEV=ppp0
+ NOPRIOHOSTSRC+ NOPRIOHOSTDST+ NOPRIOPORTSRC+ NOPRIOPORTDST+ '[' status = status ']'
+ tc -s qdisc ls dev ppp0
qdisc ingress ffff:
Sent 264605 bytes 1195 pkts (dropped 0, overlimits 0)
qdisc sfq 30: limit 128p quantum 1492b perturb 10sec
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
qdisc sfq 20: limit 128p quantum 1492b perturb 10sec
Sent 390490 bytes 610 pkts (dropped 0, overlimits 0)
qdisc sfq 10: limit 128p quantum 1492b perturb 10sec
Sent 47228 bytes 942 pkts (dropped 0, overlimits 0)
qdisc cbq 1: rate 10Mbit (bounded,isolated) prio no-transmit
Sent 437758 bytes 1553 pkts (dropped 0, overlimits 2037)
borrowed 0 overactions 0 avgidle 624 undertime 0
+ tc -s class ls dev ppp0
class cbq 1: root rate 10Mbit (bounded,isolated) prio no-transmit
Sent 40 bytes 1 pkts (dropped 0, overlimits 0)
borrowed 0 overactions 0 avgidle 624 undertime 0
class cbq 1:10 parent 1:1 leaf 10: rate 150Kbit prio 1
Sent 47288 bytes 943 pkts (dropped 0, overlimits 351)
borrowed 0 overactions 94 avgidle 624 undertime 0
class cbq 1:1 parent 1: rate 150Kbit (bounded,isolated) prio 5
Sent 437778 bytes 1553 pkts (dropped 0, overlimits 0)
borrowed 161 overactions 0 avgidle 624 undertime 0
class cbq 1:20 parent 1:1 leaf 20: rate 135Kbit prio 2
Sent 390490 bytes 610 pkts (dropped 0, overlimits 1868)
borrowed 161 overactions 263 avgidle 624 undertime 0
class cbq 1:30 parent 1:1 leaf 30: rate 120Kbit prio 2
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
borrowed 0 overactions 0 avgidle 624 undertime 0
+ exit
I hope this helps.
--
Grufl,
Michael aka. Tron
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-07-13 10:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-07-12 14:42 [LARTC] Wondershaper working, but not quite as expected Michael Frotscher
2003-07-13 4:53 ` Trevor Warren
2003-07-13 10:01 ` Michael Frotscher
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.