one more I missed is from the documentation.


# tc filter add dev eth1 protocol ip parent 1:0 prio 5 u32 ht 800:: \
        match ip src 1.2.0.0/16 \
        hashkey mask 0x000000ff at 12 \
        link 2:

Ok, some numbers need explaining. The default hash table is called 800:: and all
filtering starts there.

I don't understand the default hast table does that mean 800 is unusable?  Can
you
use a different had table for the root here? or do I have to start all
hashtables
with 800:: for their roots?



Catalin BOIE (util@deuroconsult.ro) wrote:
>
>> Is there a relation between the hashtable ID /(parent,handle)  so that
if I used 2:
>> for a hash table I could or couldn't use 2: for a (parent,handle)ID?
>No relation. You can use the same id for both.
>
>> I also noticed that you type the hashtables like 2:2:  can you have
more levels with
>> this?  like 2:2:2:1: ?  and I guess the same question with the
parent/handles.
>No, you cannot do this.
>For hashes check my previous mail, for handler: xxxxyyyy, where xxxx is
>qdisc id and yyyy is class id.
>
>>
>> thanks again.
>>
>> --
>> When dealing with a slow pipe, never underestimate the throughput of
the postal
system.
>>
>>
>> _______________________________________________
>> LARTC mailing list / LARTC@mailman.ds9a.nl
>> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>>
>
>---
>Catalin(ux aka Dino) BOIE
>catab at deuroconsult.ro
>http://kernel.umbrella.ro/
>

--
When dealing with a slow pipe, never underestimate the throughput of the postal
system.