All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] tc filter matching anything
@ 2005-07-22  2:27 Fredrik Bredeli
  2005-07-22  4:06 ` Andreas Unterkircher
  2005-07-22 13:06 ` Fredrik Bredeli
  0 siblings, 2 replies; 3+ messages in thread
From: Fredrik Bredeli @ 2005-07-22  2:27 UTC (permalink / raw)
  To: lartc

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [LARTC] tc filter matching anything
  2005-07-22  2:27 [LARTC] tc filter matching anything Fredrik Bredeli
@ 2005-07-22  4:06 ` Andreas Unterkircher
  2005-07-22 13:06 ` Fredrik Bredeli
  1 sibling, 0 replies; 3+ messages in thread
From: Andreas Unterkircher @ 2005-07-22  4:06 UTC (permalink / raw)
  To: lartc

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [LARTC] tc filter matching anything
  2005-07-22  2:27 [LARTC] tc filter matching anything Fredrik Bredeli
  2005-07-22  4:06 ` Andreas Unterkircher
@ 2005-07-22 13:06 ` Fredrik Bredeli
  1 sibling, 0 replies; 3+ messages in thread
From: Fredrik Bredeli @ 2005-07-22 13:06 UTC (permalink / raw)
  To: lartc

> 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
> 

That is great, thank you. :-)

Fredrik Bredeli
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-07-22 13:06 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-07-22  2:27 [LARTC] tc filter matching anything Fredrik Bredeli
2005-07-22  4:06 ` Andreas Unterkircher
2005-07-22 13:06 ` Fredrik Bredeli

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.