From: Marat Khalili <qm2k21@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [PATCH v4 0/4] add rpcap remote capture daemon
Date: Thu, 1 Oct 2026 19:50:34 +0100 [thread overview]
Message-ID: <cb600b10-6403-499b-af19-3f69d103510e@gmail.com> (raw)
In-Reply-To: <20261001025853.319860-1-stephen@networkplumber.org>
> pcapng: add API to read back capture mbuf header
Analysis with AI tells that there are some opportunities to make the
fast path of lib/pcapng both lighter and less .pcapng-centric to make
life of consumers that prefer other formats easier. It does not have to
(probably even shouldn't) be a part of the current patchset though.
> app/rpcapd: remote pcap daemon
Ideally forwarding captured data could run in a separate thread with
minimum unnecessary syscalls, although it's hard to tell without
benchmarks how much current design is slowed down by them.
> app/rpcapd: add TLS support
This patch simultaneously adds authentication, but it's only required
for non-loopback users. This is a common security vulnerability, not all
loopback users can be trusted. So if we care about authentication at
all, it should probably also be required for localhost users, at least
by default.
> app/rpcapd: add host list option
>
> MAINTAINERS | 2 +
> app/meson.build | 1 +
> app/rpcapd/capture.c | 541 ++++++++++++++++
> app/rpcapd/filter.c | 164 +++++
> app/rpcapd/main.c | 840 +++++++++++++++++++++++++
> app/rpcapd/meson.build | 40 ++
> app/rpcapd/rpcap-protocol.h | 146 +++++
> app/rpcapd/rpcapd.h | 122 ++++
> app/rpcapd/session.c | 292 +++++++++
> app/rpcapd/sock.c | 365 +++++++++++
> app/rpcapd/tls.c | 273 ++++++++
> app/test/test_pcapng.c | 133 ++++
> doc/guides/rel_notes/release_26_11.rst | 13 +
> doc/guides/tools/index.rst | 1 +
> doc/guides/tools/rpcapd.rst | 288 +++++++++
> lib/pcapng/rte_pcapng.c | 40 ++
> lib/pcapng/rte_pcapng.h | 46 ++
> 17 files changed, 3307 insertions(+)
> create mode 100644 app/rpcapd/capture.c
> create mode 100644 app/rpcapd/filter.c
> create mode 100644 app/rpcapd/main.c
> create mode 100644 app/rpcapd/meson.build
> create mode 100644 app/rpcapd/rpcap-protocol.h
> create mode 100644 app/rpcapd/rpcapd.h
> create mode 100644 app/rpcapd/session.c
> create mode 100644 app/rpcapd/sock.c
> create mode 100644 app/rpcapd/tls.c
> create mode 100644 doc/guides/tools/rpcapd.rst
With or without addressing any of the comments above,
Series-Acked-by: Marat Khalili <qm2k21@gmail.com>
next prev parent reply other threads:[~2026-10-01 18:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 21:07 [PATCH] examples/rpcapd: demo version of packet capture daemon Stephen Hemminger
2026-09-20 18:59 ` [PATCH v2] " Stephen Hemminger
2026-09-21 9:51 ` Marat Khalili
2026-09-21 15:57 ` Stephen Hemminger
2026-09-21 15:58 ` Stephen Hemminger
2026-09-21 16:43 ` Marat Khalili
2026-09-21 17:31 ` Stephen Hemminger
2026-09-21 17:53 ` Marat Khalili
2026-09-21 16:17 ` Stephen Hemminger
2026-09-22 18:45 ` Stephen Hemminger
2026-09-22 21:31 ` [PATCH v3] " Stephen Hemminger
2026-09-28 16:18 ` Marat Khalili
2026-09-28 17:24 ` Stephen Hemminger
2026-10-01 2:35 ` [PATCH v4 0/4] add rpcap remote " Stephen Hemminger
2026-10-01 2:35 ` [PATCH v4 1/4] pcapng: add API to read back capture mbuf header Stephen Hemminger
2026-10-01 2:35 ` [PATCH v4 2/4] app/rpcapd: remote pcap daemon Stephen Hemminger
2026-10-01 18:50 ` Marat Khalili
2026-10-01 2:35 ` [PATCH v4 3/4] app/rpcapd: add TLS support Stephen Hemminger
2026-10-01 2:35 ` [PATCH v4 4/4] app/rpcapd: add host list option Stephen Hemminger
2026-10-01 18:50 ` Marat Khalili [this message]
2026-10-01 23:00 ` [PATCH v4 0/4] add rpcap remote capture daemon Stephen Hemminger
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=cb600b10-6403-499b-af19-3f69d103510e@gmail.com \
--to=qm2k21@gmail.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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