From: Andre Correa <andre.correa@pobox.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Strange behavior deleting filters
Date: Fri, 09 Jan 2004 13:37:54 +0000 [thread overview]
Message-ID: <3FFEAEB2.6040505@pobox.com> (raw)
In-Reply-To: <3FFD829F.304@pobox.com>
The matter here is not really about using parent or handle (wich I'm
still not confortable with), but it is about the way a filter should be
deleted.
In situations like mine I cannot just delete filters by parent, because
parent qdiscs have dozens of child classes each one with a filter
poiting to it. If I have to "disable a customer", for example, I need to
delete its classes and consequently its filters, and today it is not
possible.
Using Rodrigo's trick with prio is doing the job, but doesn't look like
the right way to do it.
I'm not involved in tc, HTB or any other kernel-related development but
in my user point of view the sintax to add and delete filters should be
the same and when I delete a filter just that specific filter should be
delete, not all those that have the same prio. Maybe there was some
important problem during development that made it difficult or
impossible to be this way, we don't know yet...
Just getting back to the basic sitation, when I try (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
both filter are deleted... and it is supposed to delete just the second
filter. With or without handle the same result is reproducible in my
setup and in Rodrigo's too. Anybody else have the same behavior or it is
just us? My kernel is 2.4.23.
Anyway filters are still a bit difficult to fully understand. There are
too many undocumented options that should be described in
Advanced-Routing-HOWTO or somewhere else...
Where is the active development of tc going on for 2.4? May we report it
as a bug there?
Is the Advanced-Routing-Howto being updated? I would like to help with
it... tc is doing such a good job here that I want to give something
back to the community...
tks in advance...
Andre
Rodrigo P. Telles wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Lars,
>
> It's about the discussion of "deleting filter rules", and this "method"
> (using
> handle) was explaned by Patrick (see the list history).
>
> Telles
>
> Lars Landmark wrote:
> | Hi;
> |
> | no clue :-(
> | May I ask why you are using "handle" and not "parent" since HTB is used?
> | And what eventually are the differences?
> |
> | Lars
> |
> |
> |
> |>-----BEGIN PGP SIGNED MESSAGE-----
> |>Hash: SHA1
> |>
> |>Lars,
> |>
> |>I knew that (I use this form, but with handle, it doesn't work), but
> if what you
> |>said is truth, the folowing command would have work:
> |>
> |>tc filter del dev eth0 parent 1:0 protocol ip prio 1 handle ::12 u32
> match ip
> |>src 10.10.10.10 flowid 1:12
> |>RTNETLINK answers: No such file or directory
> |>
> |>|>tc filter add dev eth0 parent 1:0 protocol ip prio 1 handle ::12 u32
> match ip
> |>src 10.10.10.11 flowid 1:12
> |>
> |>What you thing about that ?
> |>
> |>Telles
> |>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-01-09 13:37 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
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 [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=3FFEAEB2.6040505@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.