Thank you, Andy, for your email.
So it seems that a non-leaf class is a decision point for further
classification.
On 24.04.2012 00:39, Andy Furniss wrote:
QUESTION 5: Why in filters there is used "flowid" instead of "parent"?
You can use flowid or classid this is the value you are setting for
packets that match the filter. Parent is something different it is
where the filter is attached to, usually the classid/flowid of root
but you can nest filters.
In a filter a flowid can mean a qdisc id or a class id. For example:
tc filter add dev eth0 protocol ip parent 1:0 prio 1 handle 5 fw
flowid 1:2
The filter classifies packets to class 1:2. The flowid could also be
10:0, for instance, and so it would point to a qdisc. So my idea is
to replace "flowid" with "parent" like this:
tc filter add dev eth0 protocol ip parent 1:0 prio 1 handle 5 fw
parent 1:2
But then having two "parent" parameters would be confusing.
--
Ireneusz (Irek) Szczesniak
http://www.irkos.org
--
To unsubscribe from this list: send the line "unsubscribe lartc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
