From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problem with flowid filter example from howto
Date: Thu, 21 Nov 2002 20:38:18 +0000 [thread overview]
Message-ID: <marc-lartc-103791117819101@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103790909816452@msgid-missing>
On Thursday 21 November 2002 21:02, Andrew D wrote:
> For simplicity, I tried this:
>
> tc qdisc add dev eth0 root handle 1: prio
> tc qdisc add dev eth0 parent 1:1 handle 10: sfq perturb 10
> tc qdisc add dev eth0 parent 1:2 handle 20: sfq perturb 10
> tc qdisc add dev eth0 parent 1:3 handle 30: sfq perturb 10
>
> tc filter add dev eth0 protocol ip parent 1: prio 2 flowid 1:1
>
> The last line prints:
> Unknown filter "flowid", hence option "1:1" is unparsable
>
> I'm pretty sure that last line is almost exactly what is printed
> in the howto, translated for what I want. Did I need to add
> something else first? If this is not the right syntax, how do I
> make all traffic (for now) go to a specific flow?
Try
tc filter add dev eth0 protocol ip parent 1: src 0/0 prio 2 flowid 1:1
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.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:[~2002-11-21 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 20:02 [LARTC] Problem with flowid filter example from howto Andrew D
2002-11-21 20:38 ` Stef Coene [this message]
2002-11-21 21:10 ` Andrew D
2002-11-22 15:47 ` Stef Coene
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-103791117819101@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