From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: "Wu, Yiwen" <yiwen.wu76@gmail.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] No egressing packet
Date: Wed, 16 Sep 2015 13:35:24 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B035927E73@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <55F96EFA.8050006@gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wu, Yiwen
> Sent: Wednesday, September 16, 2015 2:31 PM
> To: Thomas Monjalon
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] No egressing packet
>
> Thomas,
>
> I am using rte_eth_tx_burst to send packets. I also use
> rte_eth_add_tx_callback to register a callback to figure out what has been
> sent.
>
I would suggest checking that the source mac address is correct for all
outgoing frames as packets with an incorrect source are likely to be blocked
due to security (spoofing) concerns.
/Bruce
> Thanks,
>
> Yiwen
>
> On 9/16/2015 3:32 AM, Thomas Monjalon wrote:
> > 2015-09-15 17:10, Wu, Yiwen:
> >> 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.
> > You need to call rte_eth_tx_burst() instead of
> rte_eth_add_tx_callback().
> > For more information, please check the guide:
> >
> > http://dpdk.org/doc/guides/prog_guide/poll_mode_drv.html#poll-mode-dri
> > ver You can also check this basic example:
> > http://dpdk.org/browse/dpdk/tree/examples/skeleton/basicfwd.c
prev parent reply other threads:[~2015-09-16 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 21:10 Wu, Yiwen
2015-09-16 7:32 ` Thomas Monjalon
2015-09-16 13:30 ` Wu, Yiwen
2015-09-16 13:35 ` Richardson, Bruce [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=59AF69C657FD0841A61C55336867B5B035927E73@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=yiwen.wu76@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).