From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1868] bnxt: RTE_MBUF_F_RX_VLAN_STRIPPED set but vlan_tci is 0
Date: Thu, 22 Jan 2026 13:13:20 +0000 [thread overview]
Message-ID: <bug-1868-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1868
Bug ID: 1868
Summary: bnxt: RTE_MBUF_F_RX_VLAN_STRIPPED set but vlan_tci is
0
Product: DPDK
Version: 26.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: oleksandrn@interfacemasters.com
Target Milestone: ---
BCM957608-P2100GQF20 (235.1.157.0) with TruFlow disabled (via niccli) and
RTE_ETH_RX_OFFLOAD_VLAN_STRIP enabled doesn't set vlan_tci - it always remains
0, even though the VLAN itself is removed from the packet, and
RTE_MBUF_F_TX_VLAN and RTE_MBUF_F_RX_VLAN_STRIPPED flags are set.
- With testpmd, vlan_tci is 0 as well, type is 0x8000, so vlan is not there
anymore.
src=00:C4:7A:4C:B0:F8 - dst=00:BE:BE:BE:BE:BE - pool=mb_pool_1 - type=0x0800
- length=70 - nb_segs=1 - RSS hash=0xd65b3fd5 - RSS queue=0x5 - VLAN tci=0x0 -
hw ptype: L2_ETHER_VLAN L3_IPV4_EXT_UNKNOWN L4_UDP - sw ptype: L2_ETHER
L3_IPV4 L4_UDP - l2_len=14 - l3_len=20 - l4_len=8 - Destination UDP port=53 -
Receive queue=0x5
ol_flags: RTE_MBUF_F_RX_VLAN RTE_MBUF_F_RX_RSS_HASH
RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD
RTE_MBUF_F_RX_VLAN_STRIPPED RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
- If I do "port config 0 rx_offload vlan_strip off" RTE_MBUF_F_RX_VLAN_STRIPPED
added anyway, even though the type is 0x8100, so vlan wasn't stripped.
src=00:C4:7A:4C:B0:F8 - dst=00:BE:BE:BE:BE:BE - pool=mb_pool_1 - type=0x8100
- length=1514 - nb_segs=1 - RSS hash=0xe3688ad3 - RSS queue=0x3 - VLAN tci=0x0
- hw ptype: L2_ETHER_VLAN L3_IPV4_EXT_UNKNOWN L4_UDP - sw ptype: L2_ETHER_VLAN
L3_IPV4 L4_UDP - l2_len=18 - l3_len=20 - l4_len=8 - Receive queue=0x3
ol_flags: RTE_MBUF_F_RX_VLAN RTE_MBUF_F_RX_RSS_HASH
RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD
RTE_MBUF_F_RX_VLAN_STRIPPED RTE_MBUF_F_RX_OUTER_L4_CKSUM_UNKNOWN
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-01-22 13:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1868-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.