From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 886] mlx5 packet does not match rte_flow VXLAN if destination port is non-standard
Date: Wed, 17 Nov 2021 16:05:29 +0000 [thread overview]
Message-ID: <bug-886-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=886
Bug ID: 886
Summary: mlx5 packet does not match rte_flow VXLAN if
destination port is non-standard
Product: DPDK
Version: 21.08
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: sunnylandh@gmail.com
Target Milestone: ---
Created attachment 178
--> https://bugs.dpdk.org/attachment.cgi?id=178&action=edit
program to reproduce bug
I'm trying to use rte_flow API on ConnectX-5 Ethernet adapter with rte_net_mlx5
driver to match incoming VXLAN traffic.
If the destination UDP port is 4789, packets are received by the DPDK
application as expected.
If the destination UDP port is a non-standard port such as 14789 (specified
both on the remote host and in the flow pattern), packets are not reaching the
application.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-11-17 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 16:05 bugzilla [this message]
2022-03-13 11:25 ` 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-886-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).