From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Raj Ravi <mekaviraj@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] l2fwd application - packets not getting forwarded
Date: Fri, 13 Jun 2014 17:09:29 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B01AA36038@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAL0OjmHMP4vibGZnWGfbbj-he8Pc0Z2G7CrSn0TeNPSQqsDAGQ@mail.gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Raj Ravi
> Sent: Thursday, June 12, 2014 6:35 PM
> To: dev@dpdk.org
> Subject: Re: [dpdk-dev] l2fwd application - packets not getting forwarded
>
> Is there any requirement to modify l2fwd appliucation with updated mac
> address to make it work ?
>
> In one example, it is mentioned something similar.
> www.slideshare.net/hisaki/intel-dpdk-step-by-step-instructions
>
>
> Also, in order to make ping work it is necessary to add static entry
> for those IP addresses ?
>
> Please let me know. Thanks,
>
Hi,
In terms of using ping: the Intel DPDK works below the IP level, and the basic l2fwd sample app has no concept of an IP address or what an ICMP ping message is, so you won't get a proper ping reply out of the application as there is no IP stack to reply. What it will do, its take the ping message and forward it out a different port.
As for the more basic question of receiving packets on the NIC, normally, yes, you would need to set the destination mac address of your packets to match that of the NIC port, but in this case I believe the l2fwd app switches the port to promiscuous mode so it should receive all packets sent to it. [Other sample apps often need a "-P" flag passed to them to do this.]
Regards,
/Bruce
next prev parent reply other threads:[~2014-06-13 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 19:47 Raj Ravi
2014-06-13 1:06 ` Raj Ravi
2014-06-13 1:34 ` Raj Ravi
2014-06-13 17:09 ` Richardson, Bruce [this message]
2014-06-16 6:07 ` Raj Ravi
2014-06-22 6:09 Lu, Patrick
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=59AF69C657FD0841A61C55336867B5B01AA36038@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mekaviraj@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).