From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 531] ACL (librte_acl) Fails to match source ports
Date: Wed, 26 Aug 2020 07:41:00 +0000 [thread overview]
Message-ID: <bug-531-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=531
Bug ID: 531
Summary: ACL (librte_acl) Fails to match source ports
Product: DPDK
Version: 19.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: itamar.shoshani@ibm.com
Target Milestone: ---
After upgrading to DPDK 19.11.3, one of our regression tests failed.
A simplified version of the test that still fails is:
Creating a ruleset with two rules:
- drop udp packet with a range of source ports
- allow all udp traffic
Sending udp packet with source port outside the range
We expect the packet to be forwarded but it drops.
A workaround that work for us was replacing lib/librte_acl/acl_bld.c with the
same file from DPDK 18.11.2.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-08-26 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 7:41 bugzilla [this message]
2020-08-31 8:53 ` 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-531-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 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).