DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anudeep Kumar <anudeepnmam@gmail.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] dev Digest, Vol 231, Issue 6
Date: Mon, 21 Jan 2019 21:41:39 +0530	[thread overview]
Message-ID: <CAE0Vva4vqukUAVPD_MA9mBcKcss5vgeQudEU1A_+_ZOGrjkDVA@mail.gmail.com> (raw)
In-Reply-To: <C5EA84B2-A829-456D-BCE2-F92CF3E96C47@intel.com>

Hi Keith,

Thanks for replying,

Now able to run l3fwd application,

But once we run l3fwd application,  able to send packets using pktgen,

but if we ping packets unable to reach destination. Why this issue ?
Is there any method to ping the Packets to destination?

Regards,
Anudeep


On Mon, Jan 21, 2019, 21:27 Wiles, Keith <keith.wiles@intel.com wrote:

>
>
> > On Jan 21, 2019, at 7:23 AM, Anudeep Kumar <anudeepnmam@gmail.com>
> wrote:
> >
> > Hi,
> >
> > I am unable to run l3fwd in dpdk. Please provide steps to run.
> >
> > Regards,
> > Anudeep
> >
> > On Mon, Jan 21, 2019, 18:49 <dev-request@dpdk.org wrote:
> >
>
> Please provide much more information as to what the problem is here.
>
> DPDK version used?
> What do you mean by l3fwd does not work?
> Do you mean you can not compile DPDK or l3fwd?
> Does the l3fwd application crash or not execute?
> Does is it not find ports?
> Does is it not forward?
> What is the command line you used to build and run l3fwd plus DPDK?
>
> As you can tell you have left out a huge amount of data for us to help you?
>
> Please provide as much detail as you can, versions, machine, NICS, how you
> built DPDK, how you are testing l3fwd or the setup / configuration, too
> little information is bad.
>
> Regards,
> Keith
>
>
>

  reply	other threads:[~2019-01-21 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.14255.1548076743.7586.dev@dpdk.org>
2019-01-21 13:23 ` Anudeep Kumar
2019-01-21 15:57   ` Wiles, Keith
2019-01-21 16:11     ` Anudeep Kumar [this message]
2019-01-21 16:24       ` Wiles, Keith

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=CAE0Vva4vqukUAVPD_MA9mBcKcss5vgeQudEU1A_+_ZOGrjkDVA@mail.gmail.com \
    --to=anudeepnmam@gmail.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.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).