From: 李启闻 <pen9u1nlee@zhejianglab.com>
To: "users" <users@dpdk.org>
Subject: Usage: Unable to ping DPDK-kni-captured NIC ports
Date: Mon, 04 Sep 2023 11:26:01 +0800 [thread overview]
Message-ID: <fbab1045-7761-4191-9622-6f0814a08bdd.pen9u1nlee@zhejianglab.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 912 bytes --]
Hi,
I followed the instructions in https://doc.dpdk.org/guides-20.11/sample_app_ug/kernel_nic_interface.html <https://doc.dpdk.org/guides-20.11/sample_app_ug/kernel_nic_interface.html > to run the KNI sample application with DPDK v20.11.8.
The NIC status is shown below. Remote ping 10.11.140.8 is successful.
Firstly I bind enp3s0 to `uio_pci_generic` driver and load `rte_kni` module with carrier=off.
Then we run the sample application and it seems to be normal.
`ip addr show` prints:
Finally the IP, netmask and gw are added to the veth.
The veth is up but it is not running, and **we cannot perform a remote ping**.
My question are as follows:
1. What else need to be configured such that we could remote ping the DPDK-captured NIC?
2. Is it possible to set the IP of DPDK-captured NIC? I found that MAC\MTU could be configured but I do not find the method to configure IP.
Best wishes,
Qiwen Lee
[-- Attachment #1.2: Type: text/html, Size: 4752 bytes --]
[-- Attachment #2: temp4cj.png --]
[-- Type: application/octet-stream, Size: 20013 bytes --]
[-- Attachment #3: temp4cj.png --]
[-- Type: application/octet-stream, Size: 9794 bytes --]
[-- Attachment #4: temp4cj.png --]
[-- Type: application/octet-stream, Size: 8420 bytes --]
[-- Attachment #5: temp4cj.png --]
[-- Type: application/octet-stream, Size: 47294 bytes --]
[-- Attachment #6: temp4cj.png --]
[-- Type: application/octet-stream, Size: 5600 bytes --]
[-- Attachment #7: temp4cj.png --]
[-- Type: application/octet-stream, Size: 7683 bytes --]
[-- Attachment #8: temp4cj.png --]
[-- Type: application/octet-stream, Size: 10660 bytes --]
[-- Attachment #9: temp4cj.png --]
[-- Type: application/octet-stream, Size: 13961 bytes --]
reply other threads:[~2023-09-05 7:09 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=fbab1045-7761-4191-9622-6f0814a08bdd.pen9u1nlee@zhejianglab.com \
--to=pen9u1nlee@zhejianglab.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).