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.
This bug was initially created as a copy of Bug #2226979
I am copying this bug because:
the issue also exist in rhel8.6z
4.18.0-372.70.1.el8_6.x86_64
dpdk-21.11-2.el8_6.x86_64
Description of problem:
Server create vfs ,and set vlan to vfs.set spoofchk off and trust on. bind vfs to testpmd, send ipv6 traffic from Client, There is no packets captured in testpmd
Version-Release number of selected component (if applicable):
5.14.0-284.18.1.el9_2.x86_64
dpdk-22.11-4.el9.x86_64
5e:00.2 Ethernet controller: Broadcom Inc. and subsidiaries BCM57504 NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb/200Gb Ethernet (rev 11)
5e:00.3 Ethernet controller: Broadcom Inc. and subsidiaries BCM57504 NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb/200Gb Ethernet (rev 11)
# ethtool -i ens2f2np2
driver: bnxt_en
version: 5.14.0-284.18.1.el9_2.x86_64
firmware-version: 225.0.144.0/pkg 225.1.95.0
expansion-rom-version:
bus-info: 0000:5e:00.2
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
How reproducible:
always
Steps to Reproduce:
Server and Client is connected back to back
Server side :
1. create 1 vf on each PF
5f:02.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM5750X NetXtreme-E Ethernet Virtual Function (rev 11)
5f:03.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM5750X NetXtreme-E Ethernet Virtual Function (rev 11)
2. set vlan ,spoofchk off , trust on on vfs
#ip li set ens2f2np2 vf 0 spoofchk off
#ip li set ens2f3np3 vf 0 spoofchk off
#ip li set ens2f2np2 vf 0 trust on
#ip li set ens2f3np3 vf 0 trust on
#ip li set ens2f2np2 vf 0 vlan 2
#ip li set ens2f3np3 vf 0 vlan 2
#ip link
113: ens2f2np2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 5c:6f:69:82:8f:62 brd ff:ff:ff:ff:ff:ff
vf 0 link/ether c6:aa:3c:5e:68:dc brd ff:ff:ff:ff:ff:ff, vlan 2, spoof checking off, link-state auto, trust on
altname enp94s0f2np2
114: ens2f3np3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 5c:6f:69:82:8f:63 brd ff:ff:ff:ff:ff:ff
vf 0 link/ether f6:4b:e7:c1:23:96 brd ff:ff:ff:ff:ff:ff, vlan 2, spoof checking off, link-state auto, trust on
altname enp94s0f3np3
3.bind vf to vfio-pci, then start testpmd ,and set verbose 9 inside testpmd
#driverctl set-override 0000:5f:02.0 vfio-pci
#driverctl set-override 0000:5f:03.0 vfio-pci
#dpdk-testpmd -a 0000:5f:02.0 -a 0000:5f:03.0 -- -i --auto-start
testpmd> set verbose 9
Client side:
send ipv6 traffic with scapy
send_pkt_num = 10
size = 64
pkt = Ether()/Dot1Q(type=0x8100,vlan=2)/IPv6(src="3000::100",dst="3000::200")
pkt.dst = Client_nic2_mac ## pf mac
payload = max(0, size - len(pkt)) * 'x'
pkt.add_payload(payload.encode())
log(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 ,testpmd can receive
beaker job:
https://beaker.engineering.redhat.com/recipes/14411208#task164541163
dpdk-sriov-vf-kernel-vlan-test-spoofchk-disabled-vf-trust-on-without-max-tx-rate-without-qos-IPV6-packets-check
dpdk-sriov-vf-kernel-vlan-test-spoofchk-disabled-vf-trust-on-with-max-tx-rate-without-qos-IPV6-packets-check
dpdk-sriov-vf-kernel-vlan-test-spoofchk-disabled-vf-trust-on-without-max-tx-rate-with-qos-IPV6-packets-check
dpdk-sriov-vf-kernel-vlan-test-spoofchk-disabled-vf-trust-on-with-max-tx-rate-with-qos-IPV6-packets-check
Comment 1RHEL Program Management
2023-09-21 12:33:28 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 2RHEL Program Management
2023-09-21 14:04:10 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.