From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1926] QinQ strip not working on XL710
Date: Fri, 03 Apr 2026 18:00:49 +0000 [thread overview]
Message-ID: <bug-1926-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1926
Bug ID: 1926
Summary: QinQ strip not working on XL710
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: dmarx@iol.unh.edu
Target Milestone: ---
Packets with a single 88a8 tag, and packets with 88a8 and 8100 tags, are not
affected with qinq strip enabled:
testpmd> vlan set qinq_strip on 0
testpmd> vlan set strip on 0
Sent Dot1AD: Ether(src='40:a6:b7:22:b0:18',
dst='3c:fd:fe:c8:1a:a8')/Dot1AD()/IP(src='192.168.100.3',
dst='192.168.101.3')/UDP(sport=4321, dport=1234)/Raw(load=b'xxxxx')
Received: Ether / Dot1AD / IP / UDP 192.168.100.3:4321 > 192.168.101.3:1234 /
Raw / Padding
Sent QinQ: Ether(src='40:a6:b7:22:b0:18',
dst='3c:fd:fe:c8:1a:a8')/Dot1AD()/Dot1Q()/IP(src='192.168.100.3',
dst='192.168.101.3')/UDP(sport=4321, dport=1234)/Raw(load=b'xxxxx')
Received: Ether / Dot1AD / Dot1Q / IP / UDP 192.168.100.3:4321 >
192.168.101.3:1234 / Raw / Padding
It seems a previous ticket was closed a few years ago without resolution, which
outlined the same problem: https://bugs.dpdk.org/show_bug.cgi?id=1122
sudo ethtool -i enp181s0f0np0
driver: i40e
version: 6.8.0-106-generic
firmware-version: 9.55 0x8000fe31 1.3862.0
expansion-rom-version:
bus-info: 0000:b5:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
uname -m
x86_64
DPDK version: 26.03 rc2
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2026-04-03 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 18:00 bugzilla [this message]
2026-04-07 9:19 ` [DPDK/ethdev Bug 1926] QinQ strip not working on XL710 Bruce Richardson
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-1926-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.