From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB: Filtering flat out not working :(g
Date: Fri, 01 Mar 2002 07:50:27 +0000 [thread overview]
Message-ID: <marc-lartc-101496917318048@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101488556702466@msgid-missing>
> Perhaps i'm supposed to use this complicated route classifier of tc? Eg.
> have all packets assigned a realm thru ip route, then use tc to catch these
> packets? This is more complicated, and I don't wish to mess with my routing
> (i'm using "route", not "ip route", are these even compatible?). Ideally
> i'd like to be able to simply grab the MARKed packets with tc, let me know
> if this is possible.
>
> One additional question from my previous email that didn't get answered,
> that i'd like to know about: after adding the SFQ classes to the leafs of
> the HTB (see first post with the script in it), am I supposed to be
> attaching the filters to the 10: handles of the SFQs, or stay the way it
> is, using the HTB children eg. 1:10 ?
If a packet is outted in a class with a filter, the packet is also queued in
the qdisc that belongs to that class. This is normally a FIFO qdisc. But
you can replace it with a SFQ qdisc. So you don't need extra filter to put
the traffic in the SFQ qdisc. All packets of the class will also enter the
qdisc.
Stef
--
stef.coene@docum.org
More QOS info : http://www.docum.org/
Title : "Using Linux as bandwidth manager"
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-03-01 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 8:35 [LARTC] HTB: Filtering flat out not working :(g bert hubert
2002-02-28 15:31 ` Tim Carr
2002-03-01 7:50 ` Stef Coene [this message]
2002-03-01 10:06 ` bert hubert
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=marc-lartc-101496917318048@msgid-missing \
--to=stef.coene@docum.org \
--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.