From: Andriy Berestovskyy <aber@semihalf.com>
To: SAKTHIVEL ANAND S <anand.sa88@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Fwd: KNI not responding ingress packets
Date: Fri, 15 Apr 2016 16:40:54 +0200 [thread overview]
Message-ID: <CAOysbxrfoN27BU6Eji8SCvnQ0q5yOO11oOQ=oHGMgaCT+Ne=EQ@mail.gmail.com> (raw)
In-Reply-To: <CAOP5GAxfVSOh9L-coyf85E0DepLemT-pvT7J3KWmEgmO075e-Q@mail.gmail.com>
Hi Anand,
Make sure the KNI and NIC MACs are the same. You can also try to run
the KNI sample application in promiscuous mode (-P).
Andriy
On Mon, Apr 11, 2016 at 11:59 AM, SAKTHIVEL ANAND S
<anand.sa88@gmail.com> wrote:
> Can someone please help me pn this.. Problem In short:
>
> Linux kernel is not processing the packets received from KNI. I am using
> kernel version 3.10.0-327.el.x86_64.
>
> Thanks
> Sakthivel S
>
> ---------- Forwarded message ----------
> From: SAKTHIVEL ANAND S <anand.sa88@gmail.com>
> Date: Thu, Apr 7, 2016 at 3:15 PM
> Subject: KNI not responding ingress packets
> To: users@dpdk.org
>
>
> OM
>
> Hi
>
> I am just examining KNI sample application in DPDK-2.2.0 .
> I just compiled an launched KNI sample application, then i have configured
> IP address for the newly created KNI(assume 192.168.1.1). Then i have tried
> to ping from remote machine(192.168.1.2). After doing this i could see that
> KNI receiving the egress ARP requests and it does not responding to
> them.(even if i made static ARP on both sides, ICMP packets from remote
> machine and which is not responded or recognized by KNI/Kernel)
>
>
> can some one, please help to bring this "UP" and point out what did i
> missed on my setup.
>
> Thanks
> Sakthivel S
--
Andriy Berestovskyy
prev parent reply other threads:[~2016-04-15 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOP5GAyvLDe=tbqNOtEBMr0R5CHy0AanJwncFEr4y8wn4jOnmA@mail.gmail.com>
2016-04-11 9:59 ` SAKTHIVEL ANAND S
2016-04-15 14:40 ` Andriy Berestovskyy [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='CAOysbxrfoN27BU6Eji8SCvnQ0q5yOO11oOQ=oHGMgaCT+Ne=EQ@mail.gmail.com' \
--to=aber@semihalf.com \
--cc=anand.sa88@gmail.com \
--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).