From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Re: [PATCH v5 0/4] wireshark extcap support
Date: Sun, 25 Oct 2026 10:23:33 -0700 [thread overview]
Message-ID: <20261025102333.3ef59446@phoenix.local> (raw)
In-Reply-To: <20261016223201.608942-1-stephen@networkplumber.org>
On Fri, 16 Oct 2026 15:30:30 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:
> This series adds live packet capture from a running DPDK application
> over the telemetry socket which is usable as a source of Wireshark
> external capture (https://www.wireshark.org/docs/man-pages/extcap.html)
>
> Capture is avaliable by default but can be disabled on the command
> line with --no-capture. It works on Linux and FreeBSD.
>
> How it works:
> - The capture library registers telemetry commands (/ethdev/capture/*)
> - Callbacks are installed on the specified port/queues to copy packets
> - Packets are formatted as pcapng and written to the specified output
> - No packet data passes through the telemetry socket itself
I am going to suggest deferring this to 27.03.
Not happy with the security model, and using telemetry as the control
channel. It needs to have its own control channel, and the destination
file needs to come from the helper not get opened by DPDK process (primary).
prev parent reply other threads:[~2026-10-25 17:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 21:11 [PATCH v6 0/5] Wireshark external capture for DPDK Stephen Hemminger
2026-07-24 21:11 ` [PATCH 1/5] pcapng: extend interface statistics Stephen Hemminger
2026-07-24 21:11 ` [PATCH 2/5] capture: infrastructure wireshark packet capture Stephen Hemminger
2026-07-24 21:11 ` [PATCH 3/5] test: add test for capture hooks Stephen Hemminger
2026-07-24 21:11 ` [PATCH 4/5] usertools/dpdk-wireshark-extcap.py: script for external capture Stephen Hemminger
2026-07-24 21:11 ` [PATCH 5/5] usertools/dpdk-dumpcap: add script for file capture Stephen Hemminger
2026-07-27 22:42 ` [PATCH v2 0/4] Wireshark external capture interface Stephen Hemminger
2026-07-27 22:42 ` [PATCH v2 1/4] pcapng: extend interface statistics Stephen Hemminger
2026-07-27 22:42 ` [PATCH v2 2/4] capture: infrastructure wireshark packet capture Stephen Hemminger
2026-07-27 22:42 ` [PATCH v2 3/4] test: add test for capture hooks Stephen Hemminger
2026-07-27 22:42 ` [PATCH v2 4/4] usertools: add script for wireshark capture Stephen Hemminger
2026-07-29 23:28 ` Stephen Hemminger
2026-07-30 18:22 ` [PATCH v3 0/4] Wireshark external capture Stephen Hemminger
2026-07-30 18:22 ` [PATCH v3 1/4] pcapng: extend interface statistics Stephen Hemminger
2026-07-30 18:22 ` [PATCH v3 2/4] capture: infrastructure wireshark packet capture Stephen Hemminger
2026-07-30 18:22 ` [PATCH v3 3/4] test: add test for capture hooks Stephen Hemminger
2026-07-30 18:22 ` [PATCH v3 4/4] usertools: add script for wireshark capture Stephen Hemminger
2026-10-13 3:41 ` [PATCH v4 0/3] wireshark capture implementation Stephen Hemminger
2026-10-13 3:41 ` [PATCH v4 1/3] capture: infrastructure wireshark packet capture Stephen Hemminger
2026-10-13 3:41 ` [PATCH v4 2/3] test: add test for capture hooks Stephen Hemminger
2026-10-13 3:41 ` [PATCH v4 3/3] usertools: add script for wireshark capture Stephen Hemminger
2026-10-13 8:28 ` [PATCH v4 0/3] wireshark capture implementation fengchengwen
2026-10-13 14:19 ` Stephen Hemminger
2026-10-16 22:30 ` [PATCH v5 0/4] wireshark extcap support Stephen Hemminger
2026-10-16 22:30 ` [PATCH v5 1/4] capture: infrastructure wireshark packet capture Stephen Hemminger
2026-10-16 22:30 ` [PATCH v5 2/4] eal: add --no-capture option Stephen Hemminger
2026-10-16 22:30 ` [PATCH v5 3/4] test: add test for capture hooks Stephen Hemminger
2026-10-16 22:30 ` [PATCH v5 4/4] usertools: add script for wireshark capture Stephen Hemminger
2026-10-25 17:23 ` Stephen Hemminger [this message]
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=20261025102333.3ef59446@phoenix.local \
--to=stephen@networkplumber.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