DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1122] i40e: Rx QinQ strip does not work
Date: Wed, 09 Nov 2022 05:21:35 +0000	[thread overview]
Message-ID: <bug-1122-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=1122

            Bug ID: 1122
           Summary: i40e: Rx QinQ strip does not work
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: ivan.malov@oktetlabs.ru
  Target Milestone: ---

Test "usecases/vlan_strip_ip4" of the opensource ethdev verification suite [1]
has detected a possible bug in i40e PMD: enabling Rx QinQ stripping has no
effect.

The test sends a packet with two tags in the Ethernet header, the outer one
having TPID=0x88A8 and the inner one having TPID=0x8100. The packet arrives to
the receiver unaltered and with no indication of QinQ / VLAN presence in mbuf
flags.

The problem manifests itself in IPv6 case, too.

Should you wish to explore a detailed log example, please refer to [2]. From
over there, it is possible to observe results for other iterations exploring
the effects of various conditions.

[1] http://mails.dpdk.org/archives/dev/2022-October/251663.html
[2] https://ts-factory.io/bublik/v2/log/163204?focusId=164376&mode=treeAndlog

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2022-11-09  5:21 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-1122-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).