From: Ramandeep Sandhu <rsandhu@interrasystems.com>
To: users@dpdk.org
Subject: [dpdk-users] Unable to capture VLAN tagged Mcast packets using DPDK
Date: Wed, 5 May 2021 11:26:42 +0530 [thread overview]
Message-ID: <b2aaa11a-5452-bef9-a39b-d9ab96ec65f1@interrasystems.com> (raw)
Hello Experts,
We are capturing Multicast UDP streams using DPDK and need help with
capturing the multicast packets coming on a VLAN trunk port. The
pNIC(Intel x710) on our Linux server is connected to a trunk port on the
switch and is thus receiving packets from 2 VLANs. Our Linux server has
CentOS installed on the bare metal (/no hypervisor is being used/).
In normal case of non-VLAN traffic, we bind the physical NIC with DPDK
and create a KNI port(with a well defined IP) for it (/KNI is required
for making mutlicast join request and without KNI port we are not able
to make join requests/).
enter image description here <https://i.stack.imgur.com/Szody.png>
For VLAN traffic, the physical port of our server is connected to a
trunk port on the switch. On the Linux server, we have configured two
VLAN interfaces pNIC.10 and pNIC.20 receiving packets from VLAN 10 and
20 respectively
(/referredhttps://www.linuxtechi.com/vlan-tagged-nic-ethernet-card-centos-rhel-servers/
<https://www.linuxtechi.com/vlan-tagged-nic-ethernet-card-centos-rhel-servers/>/).
The problem we are facing is that we are unable to capture multicast
packets over a VLAN tagged port that has data coming from multiple
VLANs. Needless to say, the two VLANs have different subnets. We want to
capture multicast data coming from both 172.16.1.x and 172.16.2.x using
a single physical port on our Intel x710 NIC.
In this case, we still need to bind the physical port with DPDK as
binding happens for a PCI device id (/the VLAN IFs do not have a PCI
id/). However, we are not able to figure out what and how many KNI ports
to create. Have tried creating two KNI ports - one per VLAN ID and this
did not work for us. The KNI ports could not be enabled in this case.
Any help will be greatly appreciated !!
--
Thanks & Regards
Ramandeep Sandhu
Digital Media Group, Interra Systems.
Email : rsandhu@interrasystems.com
Ph : +91-9810980200, skype : san.raman
http://www.interrasystems.com
reply other threads:[~2021-05-05 5:56 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=b2aaa11a-5452-bef9-a39b-d9ab96ec65f1@interrasystems.com \
--to=rsandhu@interrasystems.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).