DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 617] [mlx5] packet does not match a corresponding rte_flow rule due to vxlan vni spec validation
Date: Thu, 14 Jan 2021 13:57:27 +0000	[thread overview]
Message-ID: <bug-617-3@http.bugs.dpdk.org/> (raw)


            Bug ID: 617
           Summary: [mlx5] packet does not match a corresponding rte_flow
                    rule due to vxlan vni 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 -n 4  -w 0000:00:05.0,l3_vxlan_en=1 -w 0000:00:06.0,l3_vxlan_en=1 -- -i
--rxq=5 --txq=5 --flow-isolate-all

Flow rule:

flow create 1 ingress group 0 pattern eth type is 33024  / vlan vid spec 1601 
vid prefix 8  / ipv6 src spec ::e2dd  src mask
ffff:ffff:ffff:ffff:ffff:ffff:ffff:0  proto spec 17  proto prefix 0  tc spec 0 
tc mask 0x0  / udp src is 9942  dst spec 4789  dst mask 0xffff  / vxlan vni
spec 8914560  vni mask 0x000000  / eth type is 33024  / end actions  queue
index 4 /  flag /  count / end 

The following scapy packet should match, but it doesn't:

Ether(dst='00:16:3e:64:47:7d', src='00:16:3e:13:98:e7',
type=33024)/Dot1Q(prio=0, id=0, vlan=1604, type=34525)/IPv6(version=6, tc=104,
fl=0, plen=1279, nh=17, hlim=64, src='::f299',
dst='2387:10ed:fa33:89f0:b0ac:7f2c:641d:ed5')/UDP(sport=9942, dport=4789,
len=1279, chksum=15512)/VXLAN(flags=8, reserved0=None, NextProtocol=None,
reserved1=0, gpflags=None, gpid=None, vni=4335927,
reserved2=0)/Ether(dst='00:16:3e:64:47:7d', src='00:16:3e:13:98:e7',
type=33024)/Dot1Q(prio=0, id=0, vlan=1601, type=2048)/IP(version=4, ihl=5,
tos=0, len=1245, id=1, flags=0, frag=0, ttl=64, proto=0, chksum=30750,
src='', dst='')/Raw(load=b'F'*1225) 

NIC: ConnectX-5
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.

             reply	other threads:[~2021-01-14 13:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 13:57 bugzilla [this message]
2021-01-20  8:29 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-617-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \


* 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).