[LARTC] How to write a catch all rule?

[LARTC] How to write a catch all rule?

[Unga]

Hi all

I'm new to Qos and iproute2, but studied well the
documentation.

According to
http://lartc.org/howto/lartc.qdisc.filters.html, catch
all rule should be written as follows:

tc filter add dev eth0 protocol ip parent 10: prio 2  
   \
  flowid 10:2

But it doesn't work because filtertype is missing.

Can somebody please kindly explain how to write a
catch all rule?

Many thanks in advance.

Best Regards
Unga


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

Re: [LARTC] How to write a catch all rule?

[Andreas Unterkircher]

http://mailman.ds9a.nl/pipermail/lartc/2005q3/016774.html

Unga schrieb:
> Hi all
>
> I'm new to Qos and iproute2, but studied well the
> documentation.
>
> According to
> http://lartc.org/howto/lartc.qdisc.filters.html, catch
> all rule should be written as follows:
>
> tc filter add dev eth0 protocol ip parent 10: prio 2  
>    \
>   flowid 10:2
>
> But it doesn't work because filtertype is missing.
>
> Can somebody please kindly explain how to write a
> catch all rule?
>
> Many thanks in advance.
>
> Best Regards
> Unga
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> 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

Re: [LARTC] How to write a catch all rule?

[Andy Furniss]

Andreas Unterkircher wrote:
> http://mailman.ds9a.nl/pipermail/lartc/2005q3/016774.html

tc filter add dev eth0 parent 1:0 protocol all u32 match u32 0 0 flowid 1:1


That will match all. Someone told me once that the difference between it 
working and not on a large rule set was the explicit inclusion of prio XX.

To the OP you may mean all ip (as in the lartc example) - in which case 
replace the all with ip and give it a higher prio number than the other 
rules/ put it last. Protocol all will catch arp etc aswell which may not 
be what you want./

One gotcha is that the highest prio on a filter is 1 so don't use 0 or 
that filter may be "last".

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