From: Michael Frotscher <infomails@tronserver.dyndns.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Wondershaper working, but not quite as expected
Date: Sun, 13 Jul 2003 10:01:26 +0000 [thread overview]
Message-ID: <marc-lartc-105809057124573@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105802103820881@msgid-missing>
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/
prev parent reply other threads:[~2003-07-13 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 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-105809057124573@msgid-missing \
--to=infomails@tronserver.dyndns.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox