From: "Michael P. Soulier" <michael_soulier@mitel.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] problems with tc
Date: Thu, 26 Aug 2004 12:04:40 +0000 [thread overview]
Message-ID: <20040826120440.GA29528@e-smith.com> (raw)
In-Reply-To: <marc-lartc-105474198413989@msgid-missing>
On 24/08/04 Michael P. Soulier did say:
> People,
>
> I'm trying to set up the tc filters for a PRIO queue. I'm basing it off
> of marked traffic via iptables. For example, I've marked two classes of
> traffic with ids "2" and "4", and now I'm filtering those to bands 1 and
> 2.
>
> tc filter add dev eth0 parent 1: prio 0 protocol ip \
> handle 2 fw flowid 10:1
> tc filter add dev eth0 parent 1: prio 1 protocol ip \
> handle 4 fw flowid 10:2
>
> This works fine, but now I'd like to add a "catch all" rule to send
> everything else to band 10:3. According to the Advanced Routing HOWTO,
> this should work:
>
> tc filter add dev eth0 parent 1: prio 2 flowid 10:3
>
> But, it doesn't...
>
> Unknown filter "flowid", hence option "10:3" is unparsable
>
> Also, after adding in ingress queue, I can't seem to remove it.
>
> tc qdisc del dev eth0 ingress
>
> I get: RTNETLINK answers: Invalid argument
>
> This is on an updated RedHat 7.3 box.
>
> [root@sme61a2-1 root]# uname -a
> Linux sme61a2-1 2.4.20-18.7 #1 Thu May 29 08:32:50 EDT 2003 i686 unknown
> [root@sme61a2-1 root]# rpm -q iproute
> iproute-2.4.7-7.80.1
>
> Any help appreciated.
So no one knows the answers to these questions? Perhaps the HOWTO should
be updated to reflect the fact that the commands given simply don't
work, or that the implementation is broken with certain kernels/iproute
versions. That would help greatly instead of fumbling in the dark like
this.
Cheers,
Mike
--
Michael P. Soulier <michael_soulier@mitel.com>, 613-592-2122 x2522
6000/6010/60* Development, Mitel Networks Corporation
"...the word HACK is used as a verb to indicate a massive amount of nerd-like
effort." -Harley Hahn, A Student's Guide to Unix
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-08-26 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 15:51 [LARTC] Problems with TC Lars Goldschlager
2003-06-04 17:02 ` Stef Coene
2004-08-24 18:02 ` [LARTC] problems with tc Michael P. Soulier
2004-08-26 12:04 ` Michael P. Soulier [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=20040826120440.GA29528@e-smith.com \
--to=michael_soulier@mitel.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.