From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] u32 filter won't match
Date: Sun, 23 Nov 2003 14:08:26 +0000 [thread overview]
Message-ID: <marc-lartc-106959660729587@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106956238912741@msgid-missing>
On Sunday 23 November 2003 14:44, Fredrik Tolf wrote:
> > If you add a filter to a qdisc, it has to point to a class of that
> > qdisc. Not to an other class.
>
> That confuses me a bit. It does certainly make it work, and it does
> certainly make sense. However, in the advanced routing howto, section
> 9.5.2.1, it seems to very much implicate that you can create filters
> like that. Is that howto wrong or did I misinterpret something? If you
> want to see it, follow this URL:
>
> http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.qdisc.classful.html
I know. You can do it. You can point your filter to a class of an other
qdisc and it will work, but not always like expected. To be safe, use
filters within the same qdisc.
> > > (The strange thing is that when I used "parent 2:", no filter was
> > > added at all... What's up with that?)
> >
> > Try
> > tc -s -d filter show dev eth1 parent 2:
>
> Hehe... Don't I feel stupid now... Oh well, at least now I know (I
> thought all filters were in a per-interface namespace). Thank you for
> pointing that out.
I made the same mistake before :)
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-11-23 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 4:03 [LARTC] u32 filter won't match Fredrik Tolf
2003-11-23 10:16 ` Stef Coene
2003-11-23 13:44 ` Fredrik Tolf
2003-11-23 14:08 ` Stef Coene [this message]
2003-11-23 18:46 ` Fredrik Tolf
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-106959660729587@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox