Bug ID 1188
Summary rte_acl_classify returning mismatch result
Product DPDK
Version unspecified
Hardware Other
OS Linux
Status UNCONFIRMED
Severity normal
Priority Normal
Component other
Assignee dev@dpdk.org
Reporter Utsav.Shrivastav@ibm.com
Target Milestone ---

Hi,

> Version Details 
DPDK Version : 19.11.10
Architecture : s390x (Big-Endian)
Linux OS Kernel : 5.4.0-128-generic
Ubuntu Version : 18.04.6 LTS

> Issue:
We are using ACL Library apis as part of DPDK application. As part of our
application we are trying to set following simple egress rule using function
rte_acl_add_rules():
src: 0.0.0.0/0
dst: 0.0.0.0/0
src port: 0:65535
dst port: 1:65535
protocol/mask: 6/255
category mask: 1 priority: 1 userdata: 536870912 (0x20000000)
The setting and building of rules are success.
We are then passing tcp packet to check if the same is getting matched. When we
call rte_acl_classify(), we are getting result as 0 instead of 0x2. So, a
mismatch on the protocol rule is observed and therefore packet is dropped on
egress. 

> Additional Query:
Is it possible to tell what is and how wildness is calculated for each field in
a rule?

Can you provide some insights with the issue and query ? 
Also, I am new to this DPDK bugzilla, is it possible to share any
forum/community where we can ask code-related queries (about the terms used in
code) for the purpose of  debugging ?

Regards,
Utsav
          


You are receiving this mail because: