Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Joost A. Schildwacht" <joost@schildwacht.nl>
To: lartc@vger.kernel.org
Subject: [LARTC] upstream control
Date: Sun, 08 Apr 2001 19:52:28 +0000	[thread overview]
Message-ID: <marc-lartc-98675965925973@msgid-missing> (raw)

Can somebody help me with the following;

I've defined a working downstream; the user is able to download files with a
256Kbit limit.. (btw, the 'red' policy works perfectly, thx Marian)
But, if I add the lines for the upstream, it doesn't work. (the user has the
total bandwidth for himself though I wanted to limit the bandwidth tot
32Kbit)

Please, does anybody know why the bandwidth is working for the downstream,
but not for the upstream?

Thanks in advance for you help!

Joost Schildwacht

Below the cbqconfig;

#downstream
tc qdisc add dev eth1 root handle 20: cbq bandwidth 10Mbit avpkt 1000
tc class add dev eth1 parent 20:0 classid 20:1 cbq bandwidth 10Mbit rate
10Mbit allot 1514 weight 10Mbit prio 8 maxburst 20 avpkt 1000
tc class add dev eth1 parent 20:1 classid 20:100 cbq bandwidth 10Mbit rate
256Kbit allot 1514 prio 5 maxburst 20 avpkt 1000 bounded #user
tc qdisc add dev eth1 parent 20:100 red bandwidth 256Kbit min 4500 max 9000
limit 18000 avpkt 1000 burst 5 probability 0.01
tc filter add dev eth1 parent 20:0 protocol ip prio 100 u32 match ip dst
192.168.0.199 flowid 20:100

#upstream
tc class add dev eth1 parent 20:1 classid 20:200 cbq bandwidth 10Mbit rate
32Kbit allot 1514 prio 5 maxburst 20 avpkt 1000 bounded #user
tc qdisc add dev eth1 parent 20:200 sfq quantum 1514b perturb 15
tc filter add dev eth1 parent 20:0 protocol ip prio 100 u32 match ip src
192.168.0.199 flowid 20:200



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

                 reply	other threads:[~2001-04-08 19:52 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-98675965925973@msgid-missing \
    --to=joost@schildwacht.nl \
    --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