From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: Raja Jayapal <raja.jayapal@tcs.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] capture packets on VM
Date: Fri, 15 Jul 2016 14:02:58 +0000 [thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F0105A1B4@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <OFE7FCB127.CF1C1A63-ON65257FF1.0020280D-65257FF1.00207F0D@tcs.com>
> -----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 packets
> on dpdk ports.
> I am sending traffic from host 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 inside VM.
> setup : bridge1(Host)------- VM(Guest with DPDK) ----- bridge2(Host)
>
Hi,
On DPDK you can capture packets with app/pdump/ tool. This tool is available 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 <pcap file> 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
next prev parent reply other threads:[~2016-07-15 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 5:54 Raja Jayapal
2016-07-15 12:59 ` Matt Laswell
2016-07-15 14:02 ` Pattan, Reshma [this message]
2016-07-19 11:38 ` Raja Jayapal
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=3AEA2BF9852C6F48A459DA490692831F0105A1B4@IRSMSX109.ger.corp.intel.com \
--to=reshma.pattan@intel.com \
--cc=dev@dpdk.org \
--cc=raja.jayapal@tcs.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;
as well as URLs for NNTP newsgroup(s).