From: Andreas Unterkircher <unki@netshadow.at>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc filter matching anything
Date: Fri, 22 Jul 2005 04:06:44 +0000 [thread overview]
Message-ID: <42E070D4.6040800@netshadow.at> (raw)
In-Reply-To: <20050722022736.GA21450@cocacolic.org>
You can do a "match anything" with the usage of tc-filter:
tc filter add dev eth0 parent 1:0 protocol all u32 match u32 0 0 flowid 1:1
Cheers,
Andreas
Fredrik Bredeli wrote:
>Hey,
>
>I have a problem adding a filter matching anything, here is my setup:
>
>###############
>tc qdisc add dev eth0 handle 1: root prio
>
>tc qdisc add dev eth0 parent 1:1 handle 10: pfifo
>tc qdisc add dev eth0 parent 1:2 handle 20: tbf latency 50ms rate \
>128kbit burst 256kbit
>
>tc filter add dev eth0 protocol ip parent 1:0 prio 1 handle 666 fw \
>flowid 1:2
>
>tc filter add dev eth0 protocol ip parent 1:0 prio 2 flowid 1:1
>#####################
>
>This is supposed to put all traffic marked by iptables in the tbf qdisc,
>but the last line gives me this error:
>
>error: Unknown filter "flowid", hence option "1:1" is unparsable
>
>I'm running Linux 2.4.27-2-686 with iptables v1.2.11 on debian
>sarge
>
>Does anyone know what is wrong, or have a better solution for my setup?
>
>Thank you.
>
>Fredrik Bredeli
>_______________________________________________
>LARTC mailing list
>LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-07-22 4:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 2:27 [LARTC] tc filter matching anything Fredrik Bredeli
2005-07-22 4:06 ` Andreas Unterkircher [this message]
2005-07-22 13:06 ` Fredrik Bredeli
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=42E070D4.6040800@netshadow.at \
--to=unki@netshadow.at \
--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.