All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Correa <andre.correa@pobox.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Strange behavior deleting filters
Date: Thu, 08 Jan 2004 19:02:31 +0000	[thread overview]
Message-ID: <3FFDA947.2070504@pobox.com> (raw)
In-Reply-To: <3FFD829F.304@pobox.com>


Patrick, tks for the info but I'm sure I got your idea.

A filter handle is something like: "804::800" right?

I've tried this (supose classes 1:1 and 1:2 exist):

tc filter add dev eth1 parent 1: protocol ip prio 1 handle ::10 u32 
match ip src 10.10.10.10 flowid 1:1
tc filter add dev eth1 parent 1: protocol ip prio 1 handle ::11 u32 
match ip src 10.10.10.11 flowid 1:2

and then:

tc filter del dev eth1 parent 1: protocol ip prio 1 handle ::11

but both filter are deleted...

Am I missing something?

tks a lot...

Andre



Patrick McHardy wrote:
> Andre Correa wrote:
> 
>>
>> Hi list, I'm playing with tc and found a strange behavior when I try 
>> to delete filters. For example, this simple scenario:
>>
>> tc qdisc add dev eth1 root handle 1: htb default 100
>> tc class add dev eth1 parent 1: classid 1:1 htb rate 128Kbit
>> tc class add dev eth1 parent 1: classid 1:2 htb rate 258Kbit
>> tc class add dev eth1 parent 1: classid 1:100 htb rate 32Kbit
>> tc filter add dev eth1 parent 1: protocol ip prio 1 u32 match ip src 
>> 10.10.10.20 match ip dst 63.63.63.63 flowid 1:1
>> tc filter add dev eth1 parent 1: protocol ip prio 1 u32 match ip src 
>> 10.10.10.20 flowid 1:2
>>
>> works just fine, but when I try to delete oen of the filters with 
>> something like this:
>>
>> tc filter del dev eth1 parent 1: protocol ip prio 1 u32 match ip src 
>> 10.10.10.20 flowid 1:2
>>
>> both filters are deleted.
> 
> 
> The kernel only regards priorities when deleting a filter without
> giving a handle. Use the handle if you want to delete a specific filter.
> 
> Regards,
> Patricky
> 
> 
> 

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-01-08 19:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 16:17 [LARTC] Strange behavior deleting filters Andre Correa
2004-01-08 18:02 ` Andre Correa
2004-01-08 18:46 ` Rodrigo P. Telles
2004-01-08 19:02 ` Andre Correa [this message]
2004-01-08 19:27 ` Rodrigo P. Telles
2004-01-08 20:31 ` Patrick McHardy
2004-01-08 21:26 ` Patrick McHardy
2004-01-08 22:55 ` Rodrigo P. Telles
2004-01-08 23:32 ` Rodrigo P. Telles
2004-01-09 10:45 ` Rodrigo P. Telles
2004-01-09 11:00 ` Lars Landmark
2004-01-09 11:27 ` Rodrigo P. Telles
2004-01-09 13:37 ` Andre Correa

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=3FFDA947.2070504@pobox.com \
    --to=andre.correa@pobox.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.