* [Bug 1191] rte_acl_classify returning mismatch result
@ 2023-03-16 9:33 bugzilla
2023-03-16 15:19 ` bugzilla
0 siblings, 1 reply; 2+ messages in thread
From: bugzilla @ 2023-03-16 9:33 UTC (permalink / raw)
To: dev
[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1191
Bug ID: 1191
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
rte_acl_classify() is invoked with tcp(0x6) data as argument, 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.
Can you provide some insights on the issue ?
Regards,
Utsav
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3372 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-03-16 15:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-16 9:33 [Bug 1191] rte_acl_classify returning mismatch result bugzilla
2023-03-16 15:19 ` bugzilla
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).