DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Marat Khalili <qm2k21@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] examples/rpcapd: demo version of packet capture daemon
Date: Mon, 21 Sep 2026 10:31:18 -0700	[thread overview]
Message-ID: <20260921103118.405e396c@phoenix.local> (raw)
In-Reply-To: <886c5070-d766-4119-971b-7470f71fc8c2@gmail.com>

On Mon, 21 Sep 2026 17:43:31 +0100
Marat Khalili <qm2k21@gmail.com> wrote:

> On 21/09/2026 16:58, Stephen Hemminger wrote:
> > On Mon, 21 Sep 2026 10:51:39 +0100
> > Marat Khalili <qm2k21@gmail.com> wrote:
> >  
> >>>    examples/rpcapd/meson.build            |   19 +
> >>>    examples/rpcapd/rpcap-protocol.h       |  127 +++  
> >> Could we just use one from libpcap?  
> > Could but since most distro's don't enable rpcapd the header
> > file is not exported. We could "vendor it".  
> Is it possible to use your new app without having a full version of 
> libpcap in the system (that would have this rpcap-protocol.h anyway)? In 
> "Client Setup" you mention that libpcap must be rebuilt with remote 
> support enabled, and at this moment our own abridged copy of 
> rpcap-protocol.h becomes redundant. Our copy allows building the 
> application in systems where rpcapd is missing or built without the 
> remote support, but then the build result cannot be used. Am I 
> misunderstanding something?

Read the docs, there are two issues:
 1. You need to rebuild libpcap since rpcap is a security problem,
    it is not enabled by default. Tcpdump et al will not support
    rpcap without rebuild.

 2. The rpcap-protocol.h file is not exported by libpcap and
    considered internal. The original is too damn messy to use
    in DPDK as a copy.


  reply	other threads:[~2026-09-21 17:31 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 [this message]
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

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=20260921103118.405e396c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox