Hi Team, I am using the mlx5/100G in KVM guest. The host shows this PCI vfNIC is provisioned to the guest: "17:01.1 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function]" I am using DPDK 19.11 with kind of standard configurations, and when DPDK application runs I still have the kernel mlx5e net device present. I have both promiscuous and all-multicast turned on. It works fine for IPV4, but for IPV6 it fails. It can receive packets destined to 33:33:00:00:00:02 (IPV6 Router solicitation), but cannot receive packets destined to 33:33:ff:00:00:01 (IPV6 neighbor solicitation for some address). But if I avoid DPDK, directly use the OFED-4.6 based kernel driver, everything works fine as expected. I am thinking there is some mismatch happened for MLX5 PMD. Please give some advice/hints. Many thanks Liwu *** Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. ***
06/03/2020 01:45, Liwu Liu:
> Hi Team,
>
> I am using the mlx5/100G in KVM guest. The host shows this PCI vfNIC is provisioned to the guest:
> "17:01.1 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function]"
>
> I am using DPDK 19.11 with kind of standard configurations, and when DPDK application runs I still have the kernel mlx5e net device present. I have both promiscuous and all-multicast turned on.
>
> It works fine for IPV4, but for IPV6 it fails. It can receive packets destined to 33:33:00:00:00:02 (IPV6 Router solicitation), but cannot receive packets destined to 33:33:ff:00:00:01 (IPV6 neighbor solicitation for some address).
>
> But if I avoid DPDK, directly use the OFED-4.6 based kernel driver, everything works fine as expected.
>
> I am thinking there is some mismatch happened for MLX5 PMD. Please give some advice/hints.
Adding Mellanox engineers in Cc list for help.
26/03/2020 22:11, Thomas Monjalon:
> 06/03/2020 01:45, Liwu Liu:
> > Hi Team,
> >
> > I am using the mlx5/100G in KVM guest. The host shows this PCI vfNIC is provisioned to the guest:
> > "17:01.1 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function]"
> >
> > I am using DPDK 19.11 with kind of standard configurations, and when DPDK application runs I still have the kernel mlx5e net device present. I have both promiscuous and all-multicast turned on.
> >
> > It works fine for IPV4, but for IPV6 it fails. It can receive packets destined to 33:33:00:00:00:02 (IPV6 Router solicitation), but cannot receive packets destined to 33:33:ff:00:00:01 (IPV6 neighbor solicitation for some address).
> >
> > But if I avoid DPDK, directly use the OFED-4.6 based kernel driver, everything works fine as expected.
> >
> > I am thinking there is some mismatch happened for MLX5 PMD. Please give some advice/hints.
>
> Adding Mellanox engineers in Cc list for help.
Any update to share please?
Hi Team,
I did some test today for "trusted off" vfNIC.
We use to enable (multi-unicast) promiscuous mode for vfNIC---it has no use if the vfNIC is not in trusted (super user) mode. But it masks out secondary mac address addition.
IF I turn off promiscuous mode for vfNCI, adding secondary mac then works.
+#if 1
+ struct rte_ether_addr addr = { .addr_bytes = "\x33\x33\xff\x00\x00\x01",}; <==when set this
+ rte_eth_dev_mac_addr_add(portid, &addr, 0);
+#else
+
rte_eth_promiscuous_enable(portid); <====we need to avoid this
Best,
Liwu
-----Original Message-----
From: Thomas Monjalon <thomas@monjalon.net>
Sent: Wednesday, May 6, 2020 3:05 PM
To: Liwu Liu <liwuliu@fortinet.com>
Cc: users@dpdk.org; erezf@mellanox.com; kiranv@mellanox.com; rasland@mellanox.com; asafp@mellanox.com
Subject: Re: [dpdk-users] mlx5 PMD fails to receive certain icmpv6 multicast
26/03/2020 22:11, Thomas Monjalon:
> 06/03/2020 01:45, Liwu Liu:
> > Hi Team,
> >
> > I am using the mlx5/100G in KVM guest. The host shows this PCI vfNIC is provisioned to the guest:
> > "17:01.1 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function]"
> >
> > I am using DPDK 19.11 with kind of standard configurations, and when DPDK application runs I still have the kernel mlx5e net device present. I have both promiscuous and all-multicast turned on.
> >
> > It works fine for IPV4, but for IPV6 it fails. It can receive packets destined to 33:33:00:00:00:02 (IPV6 Router solicitation), but cannot receive packets destined to 33:33:ff:00:00:01 (IPV6 neighbor solicitation for some address).
> >
> > But if I avoid DPDK, directly use the OFED-4.6 based kernel driver, everything works fine as expected.
> >
> > I am thinking there is some mismatch happened for MLX5 PMD. Please give some advice/hints.
>
> Adding Mellanox engineers in Cc list for help.
Any update to share please?