From: Matthew Hall <mhall@mhcomputing.net>
To: Daeyoung Kim <kdy1029@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK packet capture question
Date: Sun, 21 Jun 2015 19:40:06 -0700 [thread overview]
Message-ID: <1083FAEE-6E00-4B35-9626-20EBAE6F21F2@mhcomputing.net> (raw)
In-Reply-To: <CAOFzDNyt-T=uDtPq1QYM3w64niEBuvy5rLK=1Rxun2L0UM0Uww@mail.gmail.com>
On Jun 21, 2015, at 5:09 PM, Daeyoung Kim <kdy1029@gmail.com> wrote:
> I am a newbie to DPDK.
Welcome!
> I'm making a packet capture program from the l3fwd
> sample application. When I tested my program in a virtual environment, it
> worked. But in a real world, it does not work correctly.
This topology is kind of complicated.
I recommend beginning with just a single port sending ARPs, pings, etc. It takes a lot of careful work to get everything right.
Switches are going to drop some packets from different ports depending on the MAC addresses they learn from the traffic.
So if there is a switch, when beginning it is good to enable a mirror mode on two systems communicating, and sending the mirror to the DPDK port that is listening. Or use some kind of cheap 100BaseT network tap (Gigabit-plus active taps are very expensive, and not needed for simple uses like this anyway, as you don't usually send heavy traffic when just debugging).
There is also a promiscuous flag in DPDK which you usually end up needing to set if you are doing special-purpose stuff...
rte_eth_promiscuous_enable(port_id)
Good luck, happy hacking!
Matthew.
prev parent reply other threads:[~2015-06-22 2:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 0:09 Daeyoung Kim
2015-06-22 2:40 ` Matthew Hall [this message]
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=1083FAEE-6E00-4B35-9626-20EBAE6F21F2@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=kdy1029@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;
as well as URLs for NNTP newsgroup(s).