DPDK usage discussions
 help / color / mirror / Atom feed
From: Rob Zimmerman <rob@thezims.net>
To: users@dpdk.org
Subject: [dpdk-users] Debugging Dropped Frames
Date: Thu, 22 Sep 2016 13:55:34 -0400	[thread overview]
Message-ID: <CAG0K5qvg_ywYBPJ=xX68bwba-D2ODAeU2qDBoBvBrmPDfWNRhQ@mail.gmail.com> (raw)

Fellow packet wranglers,

While developing my stack I've hit an odd scenario where IP frames aren't
making it out onto the wire. Oddly enough, rte_eth_stats_get() is showing
that packets are indeed getting sent, but I'm not seeing anything on the
LAN. I can confirm part of my stack works because my ARP logic works A-OK.


Question 1)
Does DPDK drop malformed IP packets before shipping them on the wire? I've
investigated the memory segment from the ether_hdr on down, and the packet
looks fine. I ask this question because after setting the ether_type
parameter to ETHER_TYPE_ARP (on an IPv4 frame) it makes it out on the wire.
Of course, it's gobbledygook because it's actually an IPv4 frame, but at
least it made it on the wire...


Question 2)
Does DPDK perform any of its own logging that I can troll to get more
insight as to what's going on?

Thanks for the guidance!
Rob

                 reply	other threads:[~2016-09-22 17:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAG0K5qvg_ywYBPJ=xX68bwba-D2ODAeU2qDBoBvBrmPDfWNRhQ@mail.gmail.com' \
    --to=rob@thezims.net \
    --cc=users@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 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).