DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "KESHAVARAO, RASHMI" <rashmi.keshavarao@hpe.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK/ipv4_mcast sample application doesn't work
Date: Mon, 6 Sep 2021 13:50:57 +0100	[thread overview]
Message-ID: <8fcbcd78-4b6f-fcb0-4e34-34f42d83a5cb@intel.com> (raw)
In-Reply-To: <CS1PR8401MB09342B5CCA24520B55BE2452F5D29@CS1PR8401MB0934.NAMPRD84.PROD.OUTLOOK.COM>

On 9/6/2021 8:34 AM, KESHAVARAO, RASHMI wrote:
> Hi,
> We are trying to use the ipv4_multicast app in DPDK examples.
> However, we are not able to get it to run as expected.
> 
> The behavior that we are seeing is that packets are being sent from a packet generator but they are not being received by the APP. We have tried debugging the app by putting prints at various places but still don't have a clue on what is wrong.
> 
> We tried other examples apps like testpmd, l2fwd etc and these are working flawlessly.
> 
> Need inputs from the DPDK experts on the ipv4_multicast app.
> 
> Command used:
> 
> 
> ./<build_dir>/examples/ipv4_multicast -c 0x1 -n 1 -- -p 0x5 -q 2
> 
> DPDK Version: 20.08
> NIC: XXV710 (fw version: 8.3)
> Bound to: vfio-pci UIO
> 
> 
> With the above command:
> 
> *       rte_eth_rx_burst() returns 0 in the ipv4_multicast app even when packets are being sent to the NIC/port.
> 
> 
> 
> Regards,
> Rashmi.
> 

Hi Rashmi,

Most probably because packets destination MAC address is not matching to NIC MAC
address.

Can you please either test with adding 'rte_eth_promiscuous_enable(portid);'
(you can add after 'rte_eth_allmulticast_enable(portid);'),
or by setting correct destination MAC for packets?

Regards,
ferruh

      reply	other threads:[~2021-09-06 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  7:34 KESHAVARAO, RASHMI
2021-09-06 12:50 ` Ferruh Yigit [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=8fcbcd78-4b6f-fcb0-4e34-34f42d83a5cb@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=rashmi.keshavarao@hpe.com \
    /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).