All of lore.kernel.org
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] why isn't 1:1 getting the traffic? [filter question]
Date: Sat, 25 Feb 2006 03:36:19 +0000	[thread overview]
Message-ID: <43FFD0B3.1DB2A21C@iswest.com> (raw)
In-Reply-To: <20060224175729.GF3794@mandriva.com>

Andreas Hasenack wrote:
> 
> With the below script, whenever I ping 10.0.16.10 (which matches the
> only filter I have), traffic still get's sent to the default 1:2 class
> instead of 1:1 and I don't know why... Any hints?
> 
> (kernel 2.6.12, iproute2-2.6.15)
> 
> tc qdisc del dev eth0 root > /dev/null 2>&1
> tc qdisc add dev eth0 handle 1: root htb default 2
> tc class add dev eth0 classid 1:1 parent 1: htb rate 100kbps ceil 100kbps quantum 1500
> tc class add dev eth0 classid 1:2 parent 1: htb rate 90mbit ceil 90mbit quantum 1500
> tc qdisc add dev eth0 handle 2: parent 1:2 sfq perturb 10
> tc class add dev eth0 classid 1:10 parent 1:1 htb prio 0 rate 30kbps quantum 1500
> tc qdisc add dev eth0 handle 10: parent 1:10 sfq perturb 10
> tc class add dev eth0 classid 1:11 parent 1:1 htb prio 0 rate 70kbps ceil 100kbps quantum 1500
> tc qdisc add dev eth0 handle 20: parent 1:11 sfq perturb 10
> tc class add dev eth0 classid 1:12 parent 1:1 htb rate 60kbps ceil 100kbps quantum 1500
> tc qdisc add dev eth0 handle 30: parent 1:12 sfq perturb 10
> tc filter add dev eth0 parent 1:0 prio 1 protocol ip u32 \
>         match ip dst 10.0.16.10/32 \
>         flowid 1:1
> 
> Status after pinging 10.0.16.10 a few times (notice traffic on 1:2, but not on 1:1):
> qdisc htb 1: r2q 10 default 2 direct_packets_stat 0 ver 3.17
>  Sent 516 bytes 7 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 0bit 0pps backlog 0b 0p requeues 0
> qdisc sfq 2: parent 1:2 limit 128p quantum 1514b flows 128/1024 perturb 10sec
>  Sent 516 bytes 7 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 0bit 0pps backlog 0b 0p requeues 0
> qdisc sfq 10: parent 1:10 limit 128p quantum 1514b flows 128/1024 perturb 10sec
>  Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 0bit 0pps backlog 0b 0p requeues 0
> qdisc sfq 20: parent 1:11 limit 128p quantum 1514b flows 128/1024 perturb 10sec
>  Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 0bit 0pps backlog 0b 0p requeues 0
> qdisc sfq 30: parent 1:12 limit 128p quantum 1514b flows 128/1024 perturb 10sec
>  Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 0bit 0pps backlog 0b 0p requeues 0
> 
> class htb 1:11 parent 1:1 leaf 20: prio 0 quantum 1500 rate 560000bit ceil 800000bit burst 1669b/8 mpu 0b overhead 0b cburst 1699b/8 mpu 0b overhead 0b level 0
>  Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 0bit 0pps backlog 0b 0p requeues 0
>  lended: 0 borrowed: 0 giants: 0
>  tokens: 24429 ctokens: 17408
> 
> class htb 1:1 root rate 800000bit ceil 800000bit burst 1699b/8 mpu 0b overhead 0b cburst 1699b/8 mpu 0b overhead 0b level 7
>  Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 0bit 0pps backlog 0b 0p requeues 0
>  lended: 0 borrowed: 0 giants: 0
>  tokens: 17408 ctokens: 17408
> 
> class htb 1:10 parent 1:1 leaf 10: prio 0 quantum 1500 rate 240000bit ceil 240000bit burst 1629b/8 mpu 0b overhead 0b cburst 1629b/8 mpu 0b overhead 0b level 0
>  Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 0bit 0pps backlog 0b 0p requeues 0
>  lended: 0 borrowed: 0 giants: 0
>  tokens: 55636 ctokens: 55636
> 
> class htb 1:2 root leaf 2: prio 0 quantum 1500 rate 90000Kbit ceil 90000Kbit burst 12836b/8 mpu 0b overhead 0b cburst 12836b/8 mpu 0b overhead 0b level 0
>  Sent 516 bytes 7 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 8bit 0pps backlog 0b 0p requeues 0
>  lended: 7 borrowed: 0 giants: 0
>  tokens: 1164 ctokens: 1164
> 
> class htb 1:12 parent 1:1 leaf 30: prio 0 quantum 1500 rate 480000bit ceil 800000bit burst 1659b/8 mpu 0b overhead 0b cburst 1699b/8 mpu 0b overhead 0b level 0
>  Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 0bit 0pps backlog 0b 0p requeues 0
>  lended: 0 borrowed: 0 giants: 0
>  tokens: 28329 ctokens: 17408

Andreas,

Your filter looks for protocol ip.  Are you POSITIVE your ping uses ip?

Try 'protocol all' rather than 'protocol ip'.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-02-25  3:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 17:57 [LARTC] why isn't 1:1 getting the traffic? [filter question] Andreas Hasenack
2006-02-24 21:19 ` Andreas
2006-02-24 23:01 ` Andreas Klauer
2006-02-25  3:36 ` gypsy [this message]
2006-02-25 11:45 ` Andy Furniss

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=43FFD0B3.1DB2A21C@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 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.