VLAN filtering bug
https://bugs.dpdk.org/show_bug.cgi?id=1464
Bug ID: 1464
Summary: VLAN filtering bug
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Hi all,
I've written a test suite for VLAN features on DPDK drivers including filtering, stripping, and insertion, but I've run into some issues with Intel and Broadcom NICs. Both are forwarding packets when there are vlan filter rules in place which should block packet forwarding.
To recreate the environment I'm running the tests on:
drivers: bnxt_en, i40e
Broadcom NIC info:
~$ ethtool -i ens2f0np0
driver: bnxt_en
version: 5.15.0-112-generic
firmware-version: 229.0.141.0/pkg 229.1.123.0
expansion-rom-version:
bus-info: 0000:61:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
./dpdk-testpmd <EAL params> -- -i --portmask=0x3
testpmd> set fwd mac
testpmd> set promisc 0 off
testpmd> vlan set filter on 0
testpmd> rx_vlan add 1 0
testpmd> start
then, I build the following packet and send it to port 0 on testpmd:
packet = Ether()/Dot1Q(vlan=2)/Raw(load='xxxxx')
The Mellanox CX-5s show the expected behavior, where a packet with a VLAN tag not in the filter list is dropped. However, with the Intel XL710 and Broadcom 57414 NICs, the packet is forwarded regardless of whether its VLAN tag is in the filter list or not.
Link to the suite:
https://patches.dpdk.org/project/dpdk/patch/[email protected]/
Series cover letter:
https://patches.dpdk.org/project/dpdk/cover/[email protected]/
Any insight is appreciated.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
http://bugs.dpdk.org/show_bug.cgi?id=1464
Kevin Traynor ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected] Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Kevin Traynor ([email protected]) --- This is an old issue and not sure if it still exists. I will close. Please re-open if it is still an issue. Thanks.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.