From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1191] rte_acl_classify returning mismatch result
Date: Thu, 16 Mar 2023 09:33:33 +0000 [thread overview]
Message-ID: <bug-1191-3@http.bugs.dpdk.org/> (raw)
[-- 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 --]
next reply other threads:[~2023-03-16 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 9:33 bugzilla [this message]
2023-03-16 15:19 ` [Bug 1191] rte_acl_classify returning mismatch result bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1191-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.