From: Michael Barker <mikeb01@gmail.com>
To: amit sehas <cun23@yahoo.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] dpdk packet validation
Date: Sat, 28 Nov 2020 14:09:07 +1300 [thread overview]
Message-ID: <CALwNKeS8OgQ8c1FoEjQad9XLttDh6ow5dWzWk=ccZ+S=WHsaQg@mail.gmail.com> (raw)
In-Reply-To: <735250132.1304895.1606493637100@mail.yahoo.com>
If you can get a packet capture (e.g. from your switch), Wireshark can do
checksum validation. It's normally disabled by default, but if you have a
look through the Wireshark docs, there should be info on how to enable it.
Regards,
Michael Barker.
On Sat, 28 Nov 2020 at 05:14, amit sehas <cun23@yahoo.com> wrote:
> Is there some functionality that can validate packets in the same way that
> NIC validates packets such as ip header checksum
> validation etc?
>
> We are looking at some kind of bug in our code where we are exchanging
> packets at a very low rate between two devices and
> we can see that the packets are being sent from the port and are being
> received by the destination port but they never make it
> to the product ... which suggests that the NIC has dropped the packet ...
> this could happen due to checksum failure or something
> else ...
>
> earlier we had a bug which had a checksum failure and we had to fix it ...
> is there some kind of API in linux which will allow
> us to perform the same validation in s/w which is performed by the NIC in
> h/w.
>
> any help is appreciated ...
>
prev parent reply other threads:[~2020-11-28 1:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <735250132.1304895.1606493637100.ref@mail.yahoo.com>
2020-11-27 16:13 ` amit sehas
2020-11-28 1:09 ` Michael Barker [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='CALwNKeS8OgQ8c1FoEjQad9XLttDh6ow5dWzWk=ccZ+S=WHsaQg@mail.gmail.com' \
--to=mikeb01@gmail.com \
--cc=cun23@yahoo.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).