rte_acl_classify returning mismatch result
https://bugs.dpdk.org/show_bug.cgi?id=1186
Bug ID: 1186
Summary: rte_acl_classify returning mismatch result
Product: DPDK
Version: unspecified
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: [email protected]
Reporter: [email protected]
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
Quoted 1 line
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 and packet is dropped on egress gate.
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
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
https://bugs.dpdk.org/show_bug.cgi?id=1186
David Marchand ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
CC| |[email protected]
Status|UNCONFIRMED |RESOLVED--- Comment #1 from David Marchand ([email protected]) --- No need to open the same bug 4 times.
*** This bug has been marked as a duplicate of bug 1189 ***
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.