From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1165] IPv6 router solicitation and neighbor discovery packets are being sent with no reason.
Date: Thu, 23 Feb 2023 12:54:22 +0000 [thread overview]
Message-ID: <bug-1165-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1165
Bug ID: 1165
Summary: IPv6 router solicitation and neighbor discovery
packets are being sent with no reason.
Product: DPDK
Version: 21.08
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: igordptx@gmail.com
Target Milestone: ---
Created attachment 241
--> https://bugs.dpdk.org/attachment.cgi?id=241&action=edit
Output of tcpdump on a dpdk port.
I have an app running on two dpdk ports.
For some reason with no traffic being generated I am noticing a lot of IPv6
ICMP
traffic on the ports connected. I am connecting port 0 to port 1 and there is a
ton of ICMP packets. The application shouldn't generate any traffic.
From what I understand dpdk should not generate any traffic.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3115 bytes --]
reply other threads:[~2023-02-23 12:54 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-1165-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).