DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wu, Yiwen" <yiwen.wu76@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] No egressing packet
Date: Tue, 15 Sep 2015 17:10:10 -0400	[thread overview]
Message-ID: <55F88932.7020800@gmail.com> (raw)

Hi all,

I am new to dpdk. I am running a single forwarding program based on dpdk 
2.1.0. The program runs on a VM, binding on two interfaces. All it's 
doing is to forward packets from one interface to another. All 
ingressing packets are fine but there seems no egressing packets. I used 
rte_eth_add_tx_callback to register a tx callback. The callback is able 
to print the right egress packet but the destination is just not 
receiving it (via tcpdump). Does anybody have the similar experience? 
Any solution or hints will be great.

Thanks,

Yiwen

             reply	other threads:[~2015-09-15 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 21:10 Wu, Yiwen [this message]
2015-09-16  7:32 ` Thomas Monjalon
2015-09-16 13:30   ` Wu, Yiwen
2015-09-16 13:35     ` Richardson, Bruce

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=55F88932.7020800@gmail.com \
    --to=yiwen.wu76@gmail.com \
    --cc=dev@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).