From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 616] [mlx5] packet does not match a corresponding rte_flow rule due to inner ether_type spec validation
Date: Thu, 14 Jan 2021 13:54:34 +0000 [thread overview]
Message-ID: <bug-616-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=616
Bug ID: 616
Summary: [mlx5] packet does not match a corresponding rte_flow
rule due to inner ether_type spec validation
Product: DPDK
Version: 18.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
Testpmd:
"""
testpmd -n 4 -w 0000:00:05.0 -w 0000:00:06.0 -- -i --rxq=2 --txq=2
--flow-isolate-all
"""
Flow rule:
"""
flow create 0 ingress group 0 pattern eth dst is 00:16:3e:0a:11:e7 src spec
00:16:3e:25:2b:26 src prefix 0 type spec 33024 type mask 0xffff / vlan vid
spec 2213 vid prefix 1 / ipv6 / udp / vxlan vni spec 14008256 vni mask
0xffffff / eth dst is 00:16:3e:0a:11:e7 src spec 00:16:3e:25:2b:26 src
prefix 0 type spec 33024 type mask 0xffff / end actions mark id 4477696 /
queue index 1 / count / end
"""
The following scapy packet should match, but it doesn't:
"""
Ether(dst='00:16:3e:0a:11:e7', src='00:16:3e:25:2b:26',
type=33024)/Dot1Q(prio=0, id=0, vlan=4048, type=34525)/IPv6(version=6, tc=78,
fl=0, plen=243, nh=17, hlim=64, src='::252e',
dst='::1144:a5e:99f3')/UDP(sport=19036, dport=4789, len=243,
chksum=38298)/VXLAN(flags=8, reserved0=None, NextProtocol=None, reserved1=0,
gpflags=None, gpid=None, vni=14008256,
reserved2=0)/Ether(dst='00:16:3e:0a:11:e7', src='00:16:3e:25:2b:26',
type=33024)/Dot1Q(prio=0, id=0, vlan=165, type=2048)/IP(version=4, ihl=5,
tos=0, len=209, id=1, flags=0, frag=0, ttl=64, proto=0, chksum=31786,
src='127.0.0.1', dst='127.0.0.1')/Raw(load=b'X'*189)
"""
NIC: ConnectX-5
OFED: MLNX_OFED_LINUX-5.2-1.0.4.0
Firmware version: 16.29.1016
OS: RHEL 7.4
Kernel: 3.10.0-693.el7.x86_64
gcc: 4.8.5
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-01-14 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 13:54 bugzilla [this message]
2021-01-20 8:29 ` [dpdk-dev] [Bug 616] [mlx5] packet does not match a corresponding rte_flow rule due to inner ether_type spec validation 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-616-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.