DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 470] vmxnet3 pmd cannot received icmp6 ns packet
Date: Sat, 09 May 2020 11:53:19 +0000	[thread overview]
Message-ID: <bug-470-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=470

            Bug ID: 470
           Summary: vmxnet3 pmd cannot received icmp6 ns packet
           Product: DPDK
           Version: 16.04
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: longyuwlz@gmail.com
  Target Milestone: ---

Environment:

Vmware ESXi 6.5.0


vmxnet3 bind information:

Network devices using DPDK-compatible driver
============================================
0000:03:00.0 'VMXNET3 Ethernet Controller' drv=igb_uio unused=uio_pci_generic
0000:0b:00.0 'VMXNET3 Ethernet Controller' drv=igb_uio unused=uio_pci_generic


I changed vmxnet3_recv_pkts function to use rte_pktmbuf_dump dump all the mbuf
pakcet received。

I changed vmxnet3_recv_pkts like this:

+ int i;

........

 rcd_done:
+                       for (i = 0; i < nb_rx; i++) {
+                               struct rte_mbuf *m = rx_pkts[i];
+                               rte_pktmbuf_dump(stdout, m, m->pkt_len);
+                       }

Then I run our program and redirect the dump information to a file. Same time,
I used ping6 to send icmp6 ns packet in another virtual machine。

After awhile I greped icmp6 ns packet type from dumped file,but got none packet
dump information.

After that, I binded vmxnet3 to kernel driver, and setted ipv6 address,this
time the interface can received icmp6 ns packet.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-05-09 11:53 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=bug-470-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).