From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1568] fragmented icmp packets has RTE_PTYPE_L4_IGMP type instead of RTE_PTYPE_L4_FRAG
Date: Fri, 18 Oct 2024 08:14:01 +0000 [thread overview]
Message-ID: <bug-1568-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1568
Bug ID: 1568
Summary: fragmented icmp packets has RTE_PTYPE_L4_IGMP type
instead of RTE_PTYPE_L4_FRAG
Product: DPDK
Version: 22.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: balazs.barcsik@gmail.com
Target Milestone: ---
Hi There!
ICMP fragmented packets generated with following command:
hping3 --icmp -f -d 80 127.0.0.1
when calling rte_get_ptype_l4_name(pkt->packet_type) on those packets dpdk
gives back RTE_PTYPE_L4_IGMP instead of RTE_PTYPE_L4_FRAG
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2730 bytes --]
reply other threads:[~2024-10-18 8:14 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-1568-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).