Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2233755

Summary: [ice][OCP 3.0 ]vxlan fliter with ipv6 traffic doesn't forward in dpdk testpmd
Product: Red Hat Enterprise Linux 9 Reporter: Jiying Qiu <jiqiu>
Component: dpdkAssignee: Jakob Meng <jmeng>
Status: CLOSED MIGRATED QA Contact: Jiying Qiu <jiqiu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.2CC: ctrautma, fleitner, ovs-qe
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-13 18:41:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jiying Qiu 2023-08-23 09:35:14 UTC
Description of problem:
set vxlan filter inside testpmd, send ipv6 traffic from client, there is no traffic captured inside testpmd

Version-Release number of selected component (if applicable):
5.14.0-284.28.1.el9_2.x86_64
dpdk-22.11-3.el9_2.x86_64

#ethtool -i ens14f2
driver: ice
version: 5.14.0-284.28.1.el9_2.x86_64
firmware-version: 4.10 0x8001518a 1.3310.0
expansion-rom-version: 
bus-info: 0000:6c:00.2
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

#lspci
0000:6c:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)
0000:6c:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)
0000:6c:00.2 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)
0000:6c:00.3 Ethernet controller: Intel Corporation Ethernet Controller E810-C for SFP (rev 02)

#dmidecode  
.....
Handle 0x0054, DMI type 9, 24 bytes
System Slot Information
        Designation: OCP Slot 14
        Type: x16 OCP NIC 3.0 Small Form Factor (SFF)
        Current Usage: In Use
        Length: Other
        Characteristics:
                3.3 V is provided
                PME signal is supported
                PCIe slot bifurcation is supported
        Bus Address: 0000:6c:00.0
        Data Bus Width: 16
        Peer Devices: 0
....
Handle 0x0078, DMI type 203, 40 bytes
OEM-specific Type
        Header and Data:
                CB 28 78 00 54 00 FE FF 86 80 93 15 86 80 0C 00
                02 00 FE FF 00 00 05 0A 0E 01 FF FF 01 02 03 04
                FE FF 05 06 00 00 6C 00
        Strings:
                PciRoot(0x3)/Pci(0x1,0x0)/Pci(0x0,0x0)
                OCP.Slot.14.1
                Intel(R) Ethernet Network Adapter E810-XXV-4 for OCP 3.0
                OCP Slot 14
                P41616-001
                40A6B76A3DC0

How reproducible:
always

Steps to Reproduce:
Server and Client is connected back to back
Server side : 
1. bind 2 ice ports to vfio-pci
# driverctl list-overrides
0000:6c:00.2 vfio-pci
0000:6c:00.3 vfio-pci
2.start testpmd with command :
dpdk-testpmd --lcores 2-10 -a 0000:6c:00.2 -a 0000:6c:00.3 -- -i --auto-start
3.use the following commands in testpmd
testpmd>stop
testpmd>port stop all
testpmd>set verbose 9
testpmd>rx_vxlan_port add 4789 0
testpmd>rx_vxlan_port add 4789 1
testpmd>port start all
testpmd>start

Client Side:
start scapy, sent packets
send_pkt_num = 10
size = 64
pkt = Ether()/IPv6(src="3000::100",dst="3000::200")/UDP()/VXLAN()
pkt.dst = 'Client_nic2_mac'
payload = 10 * 'x'
pkt.add_payload(payload.encode())
pkt.show()
sendp(pkt,count=send_pkt_num,inter=1,iface='Client_nic1_name')

Actual results:
There is no packet captured in testpmd 

Expected results:
There should be 10 packets in testpmd, And the Client nic2 should receive 10 packets

Additional info:
send ipv4 traffic ,match the expected results.
case- dpdk_tunnel_vxlan_test

Comment 2 RHEL Program Management 2023-10-13 18:35:05 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-10-13 18:41:11 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.