DPDK usage discussions
 help / color / mirror / Atom feed
From: DoHyung Kim <dohyung.kim@fluidic.io>
To: users@dpdk.org
Subject: [dpdk-users] Sent a UDP packet, but length is wrong when captured
Date: Thu, 27 Sep 2018 03:28:44 +0900	[thread overview]
Message-ID: <034c4fb9-0f1d-78b7-0caf-6cb8c9ce2f09@fluidic.io> (raw)

Hi,

I'm new to DPDK and having trouble in crafting TX packets.

My application receives and caches UDP packets after dropping header part.
When clients request, it sends the cached packets after prepending them 
a new header mbuf
(by chaining), which contains all the headers to UDP's filled correctly 
for targeting the clients.
Though I think I'm doing nothing wrong, I see the transmitted ethernet 
frames are
14 bytes longer than expected.

Please see a capture of such a packet from Wireshark below:





The multi-seg mbuf is 1370 byte long, but weirdly enough, its 1384 when 
captured back.
I'm using libpcap based vdev on loopback interface for testing. And DPDK 
version is 17.11.3 on Ubuntu 18.04.

Any clue?

Thanks in advance.

DoHyung Kim

             reply	other threads:[~2018-09-26 18:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 18:28 DoHyung Kim [this message]
2018-09-27  1:54 ` DoHyung Kim
2018-09-27 16:24   ` DoHyung Kim

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=034c4fb9-0f1d-78b7-0caf-6cb8c9ce2f09@fluidic.io \
    --to=dohyung.kim@fluidic.io \
    --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).