From: "Dmytro O. Redchuk" <dor@ldc.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Resolved: HTB filters' parent
Date: Fri, 23 Dec 2005 08:55:05 +0000 [thread overview]
Message-ID: <20051223085505.GD5202@ldc.net> (raw)
In-Reply-To: <20051223113551.7ba9bc1d.linux@pilot.org.ua>
On Fri, Dec 23, 2005 at 11:35:51AM +0300, Denis Ovsienko wrote:
> I have examined user's configuration and found that while child classes
> had correct filters, the root qdisc hadn't any filter that could direct
> packets to lower classes. Most examples attach filters to root qdisc for
> unknown reason. The information on LARTC web-site (which is gone ATM,
> but nobody cares about that) was incorrect. You don't have to attach all
> filters to root qdisc, HTB code handles filters as well as CBQ does.
> The issue is resolved, Martin, thank you for help.
Sorry, Denis, I have missed your first message.
When I twidded with htb, I noticed that filters do work being attached to
child classes, too. There was some limitations, as far as i can remember
(filters can drop packets even to upper classes but can not drop to
different branches... or otherwise...), but it worked. It was necessary,
of course, cascade filters to have it working.
>
> --
> DO4-UANIC
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
--
_,-=._ /|_/|
`-.} `=._,.-=-._., @ @._,
`._ _,-. ) _,.-'
` G.m-"^m`m' Dmytro O. Redchuk
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-12-23 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 8:35 [LARTC] Resolved: HTB filters' parent Denis Ovsienko
2005-12-23 8:55 ` Dmytro O. Redchuk [this message]
2005-12-24 21:02 ` brick
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=20051223085505.GD5202@ldc.net \
--to=dor@ldc.net \
--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.