All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fatih Düzova" <fduzova@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Leaky bucket in TC
Date: Fri, 27 May 2005 10:23:36 +0000	[thread overview]
Message-ID: <103339c8050527032325beb2d0@mail.gmail.com> (raw)
In-Reply-To: <103339c8050526044072ea58ef@mail.gmail.com>

Thank you for your response,
My aim is to define a bandwidth (i guess it can be done by defining
equal rate and ceil values), and not to allow to pass this value "at
any moment" during the connection.  Is htb able to do this job, for
instance in the simple example below?


tc qdisc add dev ath0 root handle 1:0 htb default 15
tc class add dev ath0 parent 1:0 classid 1:1 htb rate 240kbit

tc class add dev ath0 parent 1:1 classid 1:5 htb rate 72kbit ceil 72kbit
tc class add dev ath0 parent 1:1 classid 1:10 htb rate 120kbit ceil 120kbit
tc class add dev ath0 parent 1:1 classid 1:15 htb rate 48kbit ceil 48kbit

tc qdisc add dev ath0 parent 1:5 handle 5:0 sfq perturb 10
tc qdisc add dev ath0 parent 1:10 handle 10:0 sfq perturb 10
tc qdisc add dev ath0 parent 1:15 handle 15:0 sfq perturb 10

tc filter add dev ath0 protocol ip parent 1:0 prio 1 u32 match ip
dport 22 0xffff flowid 1:5
tc filter add dev ath0 protocol ip parent 1:0 prio 1 u32 match ip
sport 22 0xffff flowid 1:5
tc filter add dev ath0 protocol ip parent 1:0 prio 1 u32 match ip
dport 80 0xffff flowid 1:10
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2005-05-27 10:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 11:40 [LARTC] Leaky bucket in TC Fatih Düzova
2005-05-27  6:08 ` Krystian Antoni
2005-05-27 10:23 ` Fatih Düzova [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=103339c8050527032325beb2d0@mail.gmail.com \
    --to=fduzova@gmail.com \
    --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.