Hello!
Seems that if I add two filters in a hash node, prio doesn't matter
anymore.
It's a known bug?
Long story:
If I do this:
echo "****************** jumptables..."
echo "*** 800: link 1:"
$tc filter add dev $dev parent 1: prio 1 u32 match ip nofrag hashkey mask 0xff000000 at 16 link 1:
echo "*** 1:1 link 2:"
$tc filter add dev $dev parent 1: prio 1 u32 ht 1:1: match ip nofrag hashkey mask 00ff0000 at 16 link 2:
echo "*** 2:2 link 3:"
$tc filter add dev $dev parent 1: prio 1 u32 ht 2:2: match ip nofrag hashkey mask 0000ff00 at 16 link 3:
echo "*** 3:3 link 4:"
$tc filter add dev $dev parent 1: prio 1 u32 ht 3:3: match ip nofrag hashkey mask 000000ff at 16 link 4:
# *************************** important part ******************************
tc filter add dev $dev parent 1: prio 2 u32 \
# ^^^
ht 4:4: match ip dst 1.2.3.4/32 flowid 1:2
tc filter add dev $dev parent 1: prio 1 u32 \
# ^^^
ht 4:4: match ip dst 1.2.3.4/32 flowid 1:3
But every ping to 1.2.3.4 goes to flowid 1:2 instead of 1:3 :(.
Thank you very much!
---
Catalin(ux) BOIE
catab@deuroconsult.ro
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
