All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Frotscher <infomails@tronserver.dyndns.org>
To: lartc@vger.kernel.org
Subject: [LARTC] Wondershaper only shaping one connection?
Date: Tue, 15 Jul 2003 18:47:46 +0000	[thread overview]
Message-ID: <marc-lartc-105829493103285@msgid-missing> (raw)

Hello, LARTC-List

I still try to get my traffic-shaping done with Wondershaper 1.1a, but it does not work
as expected. When I run the script, the verbose output looks good (using a SuSE-8.2-SMP-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: 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

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?

-- 
Sincerely,

Michael

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

                 reply	other threads:[~2003-07-15 18:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-105829493103285@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 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.