From: Stephen Hemminger <stephen@networkplumber.org>
To: Marat Khalili <qm2k21@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v4 0/4] add rpcap remote capture daemon
Date: Thu, 1 Oct 2026 16:00:46 -0700 [thread overview]
Message-ID: <20261001160046.61827fec@phoenix.local> (raw)
In-Reply-To: <cb600b10-6403-499b-af19-3f69d103510e@gmail.com>
On Thu, 1 Oct 2026 19:50:34 +0100
Marat Khalili <qm2k21@gmail.com> wrote:
> > 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.
Thought about that, and also looked at making rpcap another library
but it ends up with DPDK reimplementing libpcap...
The other option would be using dynamic fields. There already is timestamp,
but there is none for "original packet length".
Third option is not using pdump callbacks at all and just having rpcap
specific callbacks. That is what the Wireshark extcap does. That is where
I think this will end up. Would like to not use pdump since it has
so many design problems baked in.
> > 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.
New version does use a data forwarding thread.
It has to write to a socket, which it does with sendmsg.
It could use liburing, to reduce syscalls further.
> > 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.
Good point, but do not want to add DPDK specific user data base.
The problem is that TCP loopback has no way to identify who is on the
other end. Unix domain sockets do, but libpcap doesn't support that.
The real long term answer is having plugins in libpcap (Robin's proposal)
and make this one of the plugins. But that will take longer to reach
agreement on.
prev parent reply other threads:[~2026-10-01 23:00 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 ` [PATCH v4 0/4] add rpcap remote capture daemon Marat Khalili
2026-10-01 23:00 ` 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=20261001160046.61827fec@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=qm2k21@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.