From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB and tc filter
Date: Wed, 13 Sep 2006 04:06:50 +0000 [thread overview]
Message-ID: <450783DA.E78E5537@iswest.com> (raw)
In-Reply-To: <450464A2.3080205@yahoo.com.br>
> d3xcrIpt wrote:
>
> Help me ...
>
> I try use the tc filter, but seems he doesn't work, I already
> reconfigured my kernel ( 2.4.32 ) with all options related a QOS
> enabled ( like modules ) and nothing happens. I get the tc tool from
> HTB source package, well this is my set :
>
> eth0 is my internal NIC.
>
> tc qdisc add dev eth0 root handle 1: htb default 12
>
> tc class add dev eth0 parent 1: classid 1:1 htb rate 100kbps ceil
> 100kbps
> tc class add dev eth0 parent 1:1 classid 1:10 htb rate 30kbps ceil
> 100kbps
> tc class add dev eth0 parent 1:1 classid 1:11 htb rate 10kbps ceil
> 100kbps
> tc class add dev eth0 parent 1:1 classid 1:12 htb rate 60kbps ceil
> 100kbps
>
> tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip src
> <my_ip> flowid 1:10
>
> tc qdisc add dev eth0 parent handle 20: pfifo limit 5
> tc qdisc add dev eth0 parent handle 30: pfifo limit 5
> tc qdisc add dev eth0 parent handle 40: sfq perturb 10
>
> OK. but ... when I look the qdiscs
>
> tc -s -d qdisc
> qdisc htb 1: r2q 10 default 12 direct_packets_stat 411 ver 3.17
> Sent 181174 bytes 1324 pkts (dropped 0, overlimits 0)
>
> qdisc pfifo 20: parent 1:10 limit 5p
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
>
> qdisc pfifo 30: parent 1:11 limit 5p
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
>
> qdisc sfq 40: parent 1:12 quantum 1514b limit 128p flows 128/1024
> perturb 10sec
> Sent 130091 bytes 866 pkts (dropped 0, overlimits 0)
>
> All traffic is going to default class ( 1:12 ), I try many filters
> with tc tool but nothing happens.
> I look the modules with lsmod and "cls_u32.o" and "sch_htb.o" is all
> loaded.
>
> Thanks everyone.
"u32 match ip src <my_ip>"
Are you sure your IP isn't getting NATted somewhere? You can't match
something that is changed!
Include a "prio" (non zero) in your filter line.
Direct packets are A Bad Thing too. Read Devik's HTB documentation.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-09-13 4:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 19:16 [LARTC] HTB and tc filter d3xcrIpt
2006-09-13 4:06 ` gypsy [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=450783DA.E78E5537@iswest.com \
--to=gypsy@iswest.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox