All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Benitez <leonardoabenitez@gmail.com>
To: lartc@vger.kernel.org
Subject: Query about HTB qdisc
Date: Wed, 17 Apr 2013 23:58:13 +0000	[thread overview]
Message-ID: <516F3715.40000@gmail.com> (raw)

Hi

  First I'm sorry for my English

  Second:  I have a problem with my qdiscs, I have a Debian Linux router 
with a Intel Celeron 2,4 Hz processor and de following configuration not 
run correctly but the         same configuration run perfectly in other 
processor (Intel core i3).

       #!/bin/bash

        tc qdisc $1 dev $2 root handle 1:0 htb default 30

        tc class $1 dev $2 parent 1:0 classid 1:1 htb rate 300kbit ceil 
300kbit

        tc class $1 dev $2 parent 1:1 classid 1:10 htb rate 100kbit ceil 
100kbit

        tc class $1 dev $2 parent 1:1 classid 1:20 htb rate 100kbit ceil 
100kbit

        tc class $1 dev $2 parent 1:1 classid 1:30 htb rate 100kbit ceil 
100kbit


        tc qdisc $1 dev $2 parent 1:10 handle 10: sfq perturb 10

        tc qdisc $1 dev $2 parent 1:20 handle 20: sfq perturb 10

        tc qdisc $1 dev $2 parent 1:30 handle 30: sfq perturb 10


       tc filter add dev $2 parent 1:0 protocol ip prio 1 handle 1 fw 
classid 1:10

       tc filter add dev $2 parent 1:0 protocol ip prio 2 handle 2 fw 
classid 1:20

       tc filter add dev $2 parent 1:0 protocol ip prio 3 handle 3 fw 
classid 1:30

       iptables -t mangle -A PREROUTING -s 10.10.1.10 -j MARK --set-mark 1

       iptables -t mangle -A PREROUTING -s 10.10.1.10 -j RETURN


          being $1­d  and $2= eth2

     The problem is that the default traffic (30) isn't response to set 
upload values as well as the traffic outgoin of the 10.10.1.10 IP  isn't 
send to 1:10 classid, this problem
     not is find in core I3 processor.

Thanks for your time:

Leonardo A. Benitez




                 reply	other threads:[~2013-04-17 23:58 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=516F3715.40000@gmail.com \
    --to=leonardoabenitez@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.