From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 44B5F45F52; Fri, 27 Dec 2024 03:50:37 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D541E4029D; Fri, 27 Dec 2024 03:50:36 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 0E23040294 for ; Fri, 27 Dec 2024 03:50:36 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id DC6FA45F53; Fri, 27 Dec 2024 03:50:35 +0100 (CET) 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: other X-Bugzilla-Version: 23.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: junwang01@cestc.cn X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17352678350.8D24.1219091 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17352678350.8D24.1219091 Date: Fri, 27 Dec 2024 03:50:35 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1608 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=EF=BC=9A [root@xgw-dpdk /]# /dpdk/app/dpdk-dumpcap -i 0000:21:00.0=20 File: /tmp/dpdk-dumpcap_0_0000:21:00.0_20241227024137.pcapng Capturing on '0000:21:00.0' Packets captured: 108 ^C The second invocation=EF=BC=9A [root@xgw-dpdk /]# /dpdk/app/dpdk-dumpcap -i 0000:21:00.0=20 File: /tmp/dpdk-dumpcap_0_0000:21:00.0_20241227024149.pcapng pdump_prepare_client_request(): client request for pdump enable/disable fai= led EAL: Error - exiting with code: 1 Cause: Packet dump enable on 0:0000:21:00.0 failed File exists --=20 You are receiving this mail because: You are the assignee for the bug.= --17352678350.8D24.1219091 Date: Fri, 27 Dec 2024 03:50:35 +0100 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1608
Summary dpdk-dumpcap not allowed to do multiple invocations on the s= ame 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 m=
ay 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=EF=BC=9A
[root@xgw-dpdk /]# /dpdk/app/dpdk-dumpcap -i 0000:21:00.0=20
File: /tmp/dpdk-dumpcap_0_0000:21:00.0_20241227024137.pcapng
Capturing on '0000:21:00.0'
Packets captured: 108 ^C

The second invocation=EF=BC=9A
[root@xgw-dpdk /]# /dpdk/app/dpdk-dumpcap -i 0000:21:00.0=20
File: /tmp/dpdk-dumpcap_0_0000:21:00.0_20241227024149.pcapng
pdump_prepare_client_request(): client request for pdump enable/disable fai=
led
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.
=20=20=20=20=20=20=20=20=20=20
= --17352678350.8D24.1219091--