From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1608] dpdk-dumpcap not allowed to do multiple invocations on the same interface
Date: Fri, 27 Dec 2024 02:50:35 +0000 [thread overview]
Message-ID: <bug-1608-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1608
Bug ID: 1608
Summary: dpdk-dumpcap not allowed to do multiple invocations
on the same interface
Product: DPDK
Version: 23.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: junwang01@cestc.cn
Target Milestone: ---
In practical use, many scenarios may require distinguishing between inbound and
outbound traffic based on matching rules, which would necessitate calling
dpdk-dumpcap twice on the same interface. However, it seems that this is not
supported at the moment. Additionally, even when using the --file-prefix
option, the same limitation applies.
The first invocation：
[root@xgw-dpdk /]# /dpdk/app/dpdk-dumpcap -i 0000:21:00.0
File: /tmp/dpdk-dumpcap_0_0000:21:00.0_20241227024137.pcapng
Capturing on '0000:21:00.0'
Packets captured: 108 ^C
The second invocation：
[root@xgw-dpdk /]# /dpdk/app/dpdk-dumpcap -i 0000:21:00.0
File: /tmp/dpdk-dumpcap_0_0000:21:00.0_20241227024149.pcapng
pdump_prepare_client_request(): client request for pdump enable/disable failed
EAL: Error - exiting with code: 1
Cause: Packet dump enable on 0:0000:21:00.0 failed File exists
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3358 bytes --]
next reply other threads:[~2024-12-27 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 2:50 bugzilla [this message]
2025-01-15 18:47 ` [DPDK/other Bug 1608] dpdk-dumpcap not allowed to do multiple invocations on the same interface bugzilla
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-1608-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 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.