From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from inblrg02.tcs.com (inblrg02.tcs.com [121.242.48.116]) by dpdk.org (Postfix) with ESMTP id DB6892B86 for ; Tue, 19 Jul 2016 13:38:24 +0200 (CEST) IronPort-PHdr: =?us-ascii?q?9a23=3Af4Mw3x1k5U7bdNztsmDT+DRfVm0co7zxezQtwd8Z?= =?us-ascii?q?segRLfad9pjvdHbS+e9qxAeQG96Ks7QZ0qGN4+jJYi8p2d65qncMcZhBBVcuqP?= =?us-ascii?q?49uEgeOvODElDxN/XwbiY3T4xoXV5h+GynYwAOQJ6tL2PbrnD61zMOABK3bVMz?= =?us-ascii?q?fbWtXNOLxJ/nn8mJuLTrKz1SgzS8Zb4gZD6Xli728vcsvI15N6wqwQHIqHYbM8?= =?us-ascii?q?5fxGdvOE7B102kvpT41NdZ/i9Ro/Ms8dJbGeW/JvxgDO8QMDNzeVg8+NHis12L?= =?us-ascii?q?dwaU5n4VGC1CiBdTAw3MqgnzQov4tAP7sPZw3G+ROsigHp4uXjH31a5pQVfKgT?= =?us-ascii?q?YOLzc9uDXNg855yqBSsRu5rhhX34XPJoqSMawtLevmYdoGSD8ZDY5qXCtbD9b5?= =?us-ascii?q?NtNXAg=3D=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2DOAQDPDo5X/6fBE6xchRG4ZoF6hhoCg?= =?us-ascii?q?WcUAQEBAQEBAQGBC4IyBAESAYISAQEFeQwEBQYNBAMBAQEoB0YJCAYLCBG2OgE?= =?us-ascii?q?BAY5vAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIYqhE2EYIMMgi8Fjn+KJYFejm+EW?= =?us-ascii?q?YhzkB4egj4fgVRmiBABAQE?= X-IPAS-Result: =?us-ascii?q?A2DOAQDPDo5X/6fBE6xchRG4ZoF6hhoCgWcUAQEBAQEBAQG?= =?us-ascii?q?BC4IyBAESAYISAQEFeQwEBQYNBAMBAQEoB0YJCAYLCBG2OgEBAY5vAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBHIYqhE2EYIMMgi8Fjn+KJYFejm+EWYhzkB4egj4fgVR?= =?us-ascii?q?miBABAQE?= X-IronPort-AV: E=Sophos;i="5.28,389,1464633000"; d="scan'208";a="24111485" MIME-Version: 1.0 Importance: Normal X-Priority: 3 (Normal) In-Reply-To: <3AEA2BF9852C6F48A459DA490692831F0105A1B4@IRSMSX109.ger.corp.intel.com> References: <3AEA2BF9852C6F48A459DA490692831F0105A1B4@IRSMSX109.ger.corp.intel.com>, From: Raja Jayapal To: "Pattan, Reshma" Cc: "dev@dpdk.org" Message-ID: Date: Tue, 19 Jul 2016 17:08:20 +0530 X-Mailer: Lotus Domino Web Server Release 9.0.1FP6HF144 June 24, 2016 X-MIMETrack: Serialize by http on InBlrM16/TCS(Release 9.0.1FP6HF144 | June 24, 2016) at 07/19/2016 17:08:20, Serialize complete at 07/19/2016 17:08:20, Itemize by http on InBlrM16/TCS(Release 9.0.1FP6HF144 | June 24, 2016) at 07/19/2016 17:08:20, Serialize by Router on InBlrM16/TCS(Release 9.0.1FP6HF144 | June 24, 2016) at 07/19/2016 17:08:22, Serialize complete at 07/19/2016 17:08:22 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] capture packets on VM X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2016 11:38:26 -0000 Hi Reshma, = Thanks for your information. I have been trying to run the testpmd app and would like to get some idea o= n the packet flow in testpmd. br0 -----vnet0----- (port0)VM NIC br1------vnet1------(port1)VM NIC br2------vnet2------(port2)VM NIC br0 IP and MAC: fe:54:00:0d:af:af - 192.168.100.10 br1 IP and MAC: fe:54:00:4e:5b:df - 192.168.100.20 br2 IP and MAC: fe:54:00:93:78:6d - 192.168.100.30 Ran testpmd application on VM and sending packets from Host using packeth. Using PackETH generator, sent traffic from br0 destined to br1(modified the= source / destination MAC and IP in packeth tool), but i could see that the= packets are received on port0 and transmitted on port2. Sending packets from br0 to br1: ./testpmd -c 3 -n 4 -- -i --total-num-mbufs=3D3000 testpmd> show port stats all =A0 ######################## NIC statistics for port 0=A0 #################= ####### =A0 RX-packets: 4=A0=A0=A0=A0=A0=A0=A0=A0=A0 RX-missed: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 RX-bytes:=A0 0 =A0 RX-errors: 0 =A0 RX-nombuf:=A0 0=A0=A0=A0=A0=A0=A0=A0=A0 = =A0 TX-packets: 0=A0=A0=A0=A0=A0=A0=A0=A0=A0 TX-errors: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 TX-bytes:=A0 0 =A0 #######################################################################= ##### =A0 ######################## NIC statistics for port 1=A0 #################= ####### =A0 RX-packets: 0=A0=A0=A0=A0=A0=A0=A0=A0=A0 RX-missed: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 RX-bytes:=A0 0 =A0 RX-errors: 0 =A0 RX-nombuf:=A0 0=A0=A0=A0=A0=A0=A0=A0=A0 = =A0 TX-packets: 0=A0=A0=A0=A0=A0=A0=A0=A0=A0 TX-errors: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 TX-bytes:=A0 0 =A0 #######################################################################= ##### =A0 ######################## NIC statistics for port 2=A0 #################= ####### =A0 RX-packets: 0=A0=A0=A0=A0=A0=A0=A0=A0=A0 RX-missed: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 RX-bytes:=A0 0 =A0 RX-errors: 0 =A0 RX-nombuf:=A0 0=A0=A0=A0=A0=A0=A0=A0=A0 = =A0 TX-packets: 4=A0=A0=A0=A0=A0=A0=A0=A0=A0 TX-errors: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 TX-bytes:=A0 0 =A0 #######################################################################= ##### testpmd> = Second time, sent traffic from br1 to br2, but the packets are received on = port2 and transmitted on port0. Sending packets from br1 to br2: testpmd> show port stats all =A0 ######################## NIC statistics for port 0=A0 #################= ####### =A0 RX-packets: 0=A0=A0=A0=A0=A0=A0=A0=A0=A0 RX-missed: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 RX-bytes:=A0 0 =A0 RX-errors: 0 =A0 RX-nombuf:=A0 0=A0=A0=A0=A0=A0=A0=A0=A0 = =A0 TX-packets: 6=A0=A0=A0=A0=A0=A0=A0=A0=A0 TX-errors: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 TX-bytes:=A0 0 =A0 #######################################################################= ##### =A0 ######################## NIC statistics for port 1=A0 #################= ####### =A0 RX-packets: 6=A0=A0=A0=A0=A0=A0=A0=A0=A0 RX-missed: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 RX-bytes:=A0 0 =A0 RX-errors: 0 =A0 RX-nombuf:=A0 0=A0=A0=A0=A0=A0=A0=A0=A0 = =A0 TX-packets: 0=A0=A0=A0=A0=A0=A0=A0=A0=A0 TX-errors: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 TX-bytes:=A0 0 =A0 #######################################################################= ##### =A0 ######################## NIC statistics for port 2=A0 #################= ####### =A0 RX-packets: 0=A0=A0=A0=A0=A0=A0=A0=A0=A0 RX-missed: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 RX-bytes:=A0 0 =A0 RX-errors: 0 =A0 RX-nombuf:=A0 0=A0=A0=A0=A0=A0=A0=A0=A0 = =A0 TX-packets: 0=A0=A0=A0=A0=A0=A0=A0=A0=A0 TX-errors: 0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 TX-bytes:=A0 0 =A0 #######################################################################= ##### testpmd> = Could you please suggest whether this is expected behaviour? Also suggest if any configuarion needs to be done to make the flow to work = correctly. = Thanks, Raja -----"Pattan, Reshma" wrote: ----- To: Raja Jayapal From: "Pattan, Reshma" Date: 07/15/2016 07:33PM Cc: "dev@dpdk.org" Subject: RE: [dpdk-dev] capture packets on VM > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Raja Jayapal > Sent: Friday, July 15, 2016 6:55 AM > To: dev@dpdk.org > Subject: [dpdk-dev] capture packets on VM > = > Hi All, > = > I have installed dpdk on VM and would like to know how to capture the pac= kets > on dpdk ports. > I am sending traffic from host=A0 and want to know how to confirm whether= the > packets are flowing via dpdk ports. > I tried with tcpdump and wireshark but could not capture the packets insi= de VM. > setup : bridge1(Host)------- VM(Guest with DPDK) ----- bridge2(Host) > = Hi, On DPDK you can capture packets with app/pdump/ tool. This tool is availabl= e for use from 16.07RC1. = What you can do is run testpmd and see if packets are seen in testpmd, that= confirms if packets are landing on dpdk ports or not. If you also want to capture packet for analysis, you need to run app/pdump/= tool along with testpmd. = The pdump tool captures the packet to pcap file, so you can use tcpdump -ni= to view the packets. = More about the tool usage can be found under doc/guides/sample_app_ug/pdump= .rst Let me know if you need further help on this. Thanks, Reshma =3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D Notice: The information contained in this e-mail message and/or attachments to it may contain = confidential or privileged information. If you are = not the intended recipient, any dissemination, use, = review, distribution, printing or copying of the = information contained in this e-mail message = and/or attachments to it are strictly prohibited. If = you have received this communication in error, = please notify us by reply e-mail or telephone and = immediately and permanently delete the message = and any attachments. Thank you