From: Venkateswara Rao Dokku <dvrao.584@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Regarding KNI issue
Date: Tue, 2 Dec 2014 15:47:49 +0530 [thread overview]
Message-ID: <CACiOAOAOLV4SBpdrPiOM1U+wH3wiVs8QuAr8=gBXfJkE49MixQ@mail.gmail.com> (raw)
HI,
Our goal is to run traffic b/w KVM guest to linux via kni_vhost. The
topology is given below
Physical port eth1 is bound to DPDK using tools/setup.sh.
We did loaded Igb_uio module, allocated hugepages etc.
*DPDK port 0*
^
|
|
---------------------------
*Physical port(eth1)* ~~~~~~ * vEth0*
|
|
|
*eth10(different machine connected back-to-back)*
We loaded KNI module and ran the KNI applicaiton with the following command
*kni -c 0xff -n 4 -- -p 0x1 -P --config="(0,4,6)"*
and we could see vEth0 added in kernel.
1. Now, How can we test traffic with the KNI interface to external world. ??
We were not able to ping between *vEth0* and *eth10*.
2. We launched a KVM guest machine, and provided *vEth0* as the tap
interface. When we initiated ping to *eth10* from the guest, we can see the
arp requests on* vEth0 (saw in tcpdump)*. But these packets are not
reaching *eth10. * If we ping from *eth10*, we dont see any packets on
*vEth0*.
Do we need to do any other configuration other than this?
Any help is much appreciated.
--
Thanks & Regards,
Venkateswara Rao Dokku
reply other threads:[~2014-12-02 10:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CACiOAOAOLV4SBpdrPiOM1U+wH3wiVs8QuAr8=gBXfJkE49MixQ@mail.gmail.com' \
--to=dvrao.584@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).