From: "Rodrigo P. Telles" <telles@devel-it.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Strange behavior deleting filters
Date: Thu, 08 Jan 2004 22:55:06 +0000 [thread overview]
Message-ID: <3FFDDFCA.60005@devel-it.com.br> (raw)
In-Reply-To: <3FFD829F.304@pobox.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andre,
I don't now, when I've had that problem, I didn't find anything about that !
I've tried to report this problem, but all mails that I sent to the list, they
had simply desappeared, and I've found this "solution" (for my case this
solution is good). Later, my mail was started to work and I forgot to notify the
list about that.
I remembered that when I saw your mail about filter rules :-)
I expect that someone have an idea about that, because is impossible that only
you and me are having this behavior.
Telles
Andre Correa wrote:
|
| Hi Rodrigo, tks for the answer. It sounds like a starting point but this
| is not that good if there are several filters pointing to classes with
| high load. In this case lower prio classes will really have higher
| priority.
|
| Isn't it supposed to work as expected: delete only the right filter? May
| it be reported as a bug? Is it a known behavior?
|
| tks...
|
| Andre
|
|
| Rodrigo P. Telles wrote:
|
|> -----BEGIN PGP SIGNED MESSAGE-----
|> Hash: SHA1
|>
|> Andre,
|>
|> I've had the same problem when I try to remove one filter rule.
|> This is ocurred when you have the same prio for all filter rules. I've
|> "solved"
|> my problem using diferent "prio" values in filter rules.
|> I don't now if this is a BUG !
|>
|> Anything else ?
|>
|> Telles
|>
|> 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.
|> |
|> | I've found a post from Dimitry V. Ketov in the kernel list on may/2003
|> | with a situation like this one, but there are no answers.
|> |
|> | I'm using 2.4.23 and iptables 1.2.7a. Any clues what can be the cause?
|> | I'm suposed to be able to delete filters separately right? May it be
|> a bug?
|> |
|> | Deleting the whole qdisc is not an opition in my setup and trying to
|> | delete the parent class gives me a "device or resource busy" error
|> | because of the filters. tc class del doesn't seen to delete its "child"
|> | filter.
|> |
|> | tks for any information...
|> |
|> | Andre
|> |
|> | _______________________________________________
|> | LARTC mailing list / LARTC@mailman.ds9a.nl
|> | http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
|> |
|> |
|>
|> - --
|> - ------------------------------------------------------
|> Rodrigo P. Telles <telles@devel-it.com.br>
|> Gerente de Projetos - http://www.devel-it.com.br
|> Devel-IT - Uma empresa do Grupo TDKOM
|> - ------------------------------------------------------
|> -----BEGIN PGP SIGNATURE-----
|> Version: GnuPG v1.0.7 (GNU/Linux)
|> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
|>
|> iD8DBQE//aWeiLK8unYgEMQRAgPcAJ9iqsF9V5m4QqKrLgI3iUF6rLW8hACeJ0GP
|> 6DYjQf0/5NVNRrojAXvgcw8|> ÐPR
|> -----END PGP SIGNATURE-----
|>
|> _______________________________________________
|> LARTC mailing list / LARTC@mailman.ds9a.nl
|> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
|>
|>
|
| _______________________________________________
| LARTC mailing list / LARTC@mailman.ds9a.nl
| http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
|
|
|
- --
- ------------------------------------------------------
Rodrigo P. Telles <telles@devel-it.com.br>
Gerente de Projetos - http://www.devel-it.com.br
Devel-IT - Uma empresa do Grupo TDKOM
- ------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE//d/KiLK8unYgEMQRAlgLAJ4torQ3qVFfOLujnSMiFUkKG+CiIgCfZ2q9
jTggAS7kT2eIyiMnNqeEvEk=bzBz
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-01-08 22:55 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 [this message]
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=3FFDDFCA.60005@devel-it.com.br \
--to=telles@devel-it.com.br \
--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.