Ethy H. Brito wrote:
Hi All
If I redirect to an interface with
/sbin/tc qdisc add dev eth0 ingress
/sbin/tc filter add dev eth0 parent ffff: protocol all prio 1 \
u32 match u32 0 0 flowid 1:2 \
action mirred egress redirect dev ifb0
Given that setup I can say:
1) all packets incoming thru eth0 will be *MOVED* to ifb0 output and do not
return to eth0.
I don't know what return to eth0 would mean for ingress - but I expect
(untested), if you had some netfilter rule that said -i eth0 that it
would still work for a packet that went through the ifb.
2) flowid X:Y is of no importance. I can write anything for X:Y.
I think that these get reinstated when the packet leaves ifb, which
could I suppose affect things if it goes through another qdisc (I guess
this would apply to egress more than ingress, eg. pfifo fast being default).
Are these assertives correct??
I don't know for sure, you need to test.
--
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
