archive mirror
 help / color / mirror / Atom feed
From: Kumar Thangavel <>
To: "" <>
Cc: "Velumani T-ERS, HCLTech" <>,
	Amithash Prasad <>
Subject: Ethernet Raw socket not sending with pldm payload size more than 24 bytes
Date: Thu, 18 Mar 2021 06:41:48 +0000	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 2365 bytes --]

Classification: Public
Hi All,

         We are working on pldm over NCSI NIC firmware update feature. We are using Raw socket to send the NCSI packets to NIC cards.
         This raw socket is working for the pldm over NCSI sensor commands. Pldm sensor commands having pldm payload as 6 bytes length only. We could see it in the tcpdump.

         The same raw socket is not working for pldm over NCSI NIC firmware update commands.
         We are facing issues if we send the pldm payload length more than 24 bytes.
         The commands are not sending with the pldm payload length of more than 24 bytes. Not sending in the TCP stack itself. That is also not captured in tcpdump.

         In the raw socket, We framed the packet like Ethernet header - 14 bytes, ncsi header - 16 bytes, pldm payload - 28 bytes.
         So, The commands are not sending if we send ethernet payload size greater than 54 bytes.

         But if we send less than 54, the commands are sending properly and got correct responses.
         We tried with ncsi netlink library also to send the commands. There also we are facing same issue.

         Could you please point us if there is any known issues or workaround for this issue.


The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.

[-- Attachment #2: Type: text/html, Size: 5527 bytes --]

                 reply	other threads:[~2021-03-18  6:43 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).