All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB droping packets
Date: Sat, 24 Dec 2005 17:18:56 +0000	[thread overview]
Message-ID: <43AD8300.8090804@dsl.pipex.com> (raw)
In-Reply-To: <20051221135538.M20919@tim.ro>

Andy Furniss wrote:
> Dumitrache Ionut wrote:
> 
>> Hello,
>>
>>     I'm using htb3 with kernel 2.6.13 on debian testing release. I have a
>> hierarchy consisting of 10 parents clas each with 2 to 20 childs and 
>> every
>> child use sfq. The problem is when the default class become congested, 
>> the
>> system start to drop packets for 2 seconds all traffic is blocked, 
>> another 3
>> to 5  minutes all goes all and so on.     Anyone have any ideea about 
>> this ?
> 
> 
> Your arp traffic is probably going to default - either don't use htb 
> default or filter ... protocol arp u32 match u32 0 0 ... to a high 
> prio/bandwidth class.

"I don't know where you're getting your tc, because the current iproute2
does not have "protocol arp".

Could you please explain (to the LARTC list) how you make the above
work?
--
gypsy"

I am a bit behind on kernels but will try the latest of everything soon.

In the past I failed to get protocol all to work then I tried again and 
it did. Whenever I try things with tc and fail I always start again from 
the beginning with tc qdisc del dev

[root@amd /home/andy/Qos]# tc -V
tc utility, iproute2-ss050330

[root@amd /home/andy/Qos]# tc qdisc add dev eth0 root handle 1:0 htb
[root@amd /home/andy/Qos]# tc filter add dev eth0 parent 1:0 protocol 
arp u32 match u32 0 0
[root@amd /home/andy/Qos]# tc -s filter ls dev eth0
filter parent 1: protocol arp pref 49152 u32
filter parent 1: protocol arp pref 49152 u32 fh 800: ht divisor 1
filter parent 1: protocol arp pref 49152 u32 fh 800::800 order 2048 key 
ht 800 bkt 0  (rule hit 0 success 0)
   match 00000000/00000000 at 0 (success 0 )
[root@amd /home/andy/Qos]# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttld time=1.319 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttld time=0.295 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttld time=0.311 ms
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.295/0.642/1.319/0.479 ms
[root@amd /home/andy/Qos]# tc -s filter ls dev eth0
filter parent 1: protocol arp pref 49152 u32
filter parent 1: protocol arp pref 49152 u32 fh 800: ht divisor 1
filter parent 1: protocol arp pref 49152 u32 fh 800::800 order 2048 key 
ht 800 bkt 0  (rule hit 1 success 0)
   match 00000000/00000000 at 0 (success 1 )
[root@amd /home/andy/Qos]# tc -V
tc utility, iproute2-ss050330

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2005-12-24 17:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 13:59 [LARTC] HTB droping packets Dumitrache Ionut
2005-12-23  2:50 ` Andy Furniss
2005-12-24 17:18 ` Andy Furniss [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=43AD8300.8090804@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.