From: Franck BAUDIN <Franck.BAUDIN@qosmos.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Wrong TCP checksum of packets sent by Linux guest (virtIO/vhost)
Date: Tue, 2 Sep 2014 13:20:08 +0000 [thread overview]
Message-ID: <D84D5A6C1B26E448A0F35B539111D0E721D8C0@CAROUBIER.jungle.qosmos.com> (raw)
Hello,
This is a repost of https://lists.01.org/pipermail/dpdk-ovs/2014-September/001788.html as the issue might be related to dpdk.org vhost code.
I am using dpdk-ovs 1.1.0 (latest release) as follow :
linux-guest (no DPKD) <--- virtIO ---> OVDK 1.1.0 (with latest DPDK [*]) < --- Niantic --- > linux-native
[*] commit 8fd8bebc051704d7caecfed8d8a065a79c022329
Author: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Mon Sep 1 12:31:11 2014 +0200
UDP/ICMP connectivity is fine, but TCP checksum of packet sent by the guest are incorrect, as showed with tcpdump on linux-native.
Is it supposed to work? If yes, what is the proper qemu version to use and its parameters?
I am using qemu version provided by dpdk-ovs (same issue with PDDK 1.7.0 and latest one) and I followed this documentation: https://github.com/01org/dpdk-ovs/blob/development/docs/04_Sample_Configurations/02_Userspace-vHost.md
Thanks!
Franck
This message and any attachments (the "message") are confidential, intended solely for the addressees. If you are not the intended recipient, please notify the sender immediately by e-mail and delete this message from your system. In this case, you are not authorized to use, copy this message and/or disclose the content to any other person. E-mails are susceptible to alteration. Neither Qosmos nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.
Ce message et toutes ses pièces jointes (ci-après le "message")sont confidentiels et établis à l'intention exclusive de ses destinataires. Si vous avez reçu ce message par erreur, merci d’en informer immédiatement son émetteur par courrier électronique et d’effacer ce message de votre système. Dans cette hypothèse, vous n’êtes pas autorisé à utiliser, copier ce message et/ou en divulguer le contenu à un tiers. Tout message électronique est susceptible d'altération. Qosmos et ses filiales déclinent toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié.
next reply other threads:[~2014-09-02 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 13:20 Franck BAUDIN [this message]
2014-09-02 13:29 ` Thomas Monjalon
2014-09-02 14:37 ` Franck Baudin
2014-09-03 10:00 ` Gray, Mark D
2014-09-03 11:13 ` Xie, Huawei
2014-09-03 14:12 ` Franck Baudin
2014-09-03 16:07 ` Gray, Mark D
2014-09-04 2:54 ` Xie, Huawei
2014-09-04 9:24 ` Franck Baudin
2014-09-04 10:35 ` Xie, Huawei
2014-09-03 16:15 ` Gray, Mark D
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=D84D5A6C1B26E448A0F35B539111D0E721D8C0@CAROUBIER.jungle.qosmos.com \
--to=franck.baudin@qosmos.com \
--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).