From: Alex Markuze <alex@weka.io>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] UDP Checksum
Date: Thu, 6 Nov 2014 18:05:28 +0200 [thread overview]
Message-ID: <CAKfHP0WWCrftSR=z=jvUsHCLtTZdBwch0ZvadiLa9nMfcbpW-Q@mail.gmail.com> (raw)
Hi,
I'm seeing "UDP: bad checksum." messages(dmesg) for packets sent by my dpdk
app to a socket on a remote machine.
Looking at the packets the scum value is set, its just not what wireshark
expects.
When sending I'm setting these fields in the egress packets.
pkt->pkt.vlan_macip.f.l2_len = sizeof(struct ether_hdr);
pkt->pkt.vlan_macip.f.l3_len = sizeof(struct ipv4_hdr);
pkt->ol_flags |= (PKT_TX_IP_CKSUM | PKT_TX_L4_MASK);
//PKT_TX_OFFLOAD_MASK;
I'm working with a 82599 VF.
Any thoughts? I'm not sure what else to check.
next reply other threads:[~2014-11-06 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 16:05 Alex Markuze [this message]
2014-11-06 16:15 ` Olivier MATZ
2014-11-06 16:15 ` Ananyev, Konstantin
2014-11-06 16:26 ` Alex Markuze
[not found] ` <2601191342CEEE43887BDE71AB977258213A2EC5@IRSMSX105.ger.corp.intel.com>
2014-11-06 17:07 ` Ananyev, Konstantin
2019-09-24 15:11 [dpdk-dev] udp checksum Khoussi, Siham (IntlAssoc)
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='CAKfHP0WWCrftSR=z=jvUsHCLtTZdBwch0ZvadiLa9nMfcbpW-Q@mail.gmail.com' \
--to=alex@weka.io \
--cc=dev@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).