Re: rte flow rule not clear with DPDK 21.11 and Intel E810

[Filip Janiszewski <contact@filipjaniszewski.com>]

Just updating on other similar issue I'm finding, it appears this rte
flow rule is completely broken for Intel E810 and most probably useless,
for example, this rule works:

.
testpmd> flow create 0 ingress pattern eth / ipv4 / tcp dst is 2044 /
end actions queue index 1 / end
Flow rule #4 created
.

But the UDP version does not work:

.
testpmd> flow create 0 ingress pattern eth / ipv4 / udp dst is 51005 /
end actions queue index 1 / end
Flow rule #1 created
.

Also vlan id based filtering do not work, ip ranges (using spec+last) do
not work et cetera.

Am I doing something wrong with testpmd or anybody can confirm that this
is just not working until fixed?

Thanks

Il 12/1/21 8:48 AM, Filip Janiszewski ha scritto:
> Hi,
> 
> Is there any sensible reason for which this flow rule works:
> 
> .
> testpmd> flow create 0 ingress pattern eth / ipv4 dst spec 199.168.152.2
> dst mask 255.255.0.255 / end actions queue index 1 / end
> Flow rule #0 created
> .
> 
> But this one not?:
> 
> .
> testpmd> flow create 0 ingress pattern eth / ipv4 dst spec 199.168.152.2
> dst mask 255.255.255.0 / end actions queue index 1 / end
> ice_flow_create(): Failed to create flow
> port_flow_complain(): Caught PMD error type 10 (item specification):
> cause: 0x7ffe040edaa8, Invalid input set: Invalid argument
> .
> 
> I've just changed the mask from 255.255.0.255 to 255.255.255.0, it's
> really confusing why the latter one is not accepted..
> 
> Thanks
> 

-- 
BR, Filip
+48 666 369 823