mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Mat Martineau <mathew.j.martineau@linux.intel.com>,
	Matthieu Baerts <matthieu.baerts@tessares.net>,
	Geliang Tang <geliangtang@gmail.com>
Cc: mptcp@lists.linux.dev
Subject: Re: MPTCP checksum interop
Date: Mon, 14 Jun 2021 10:30:42 +0200	[thread overview]
Message-ID: <8cceb711ad974911da62d62a354e6569b573e0b2.camel@redhat.com> (raw)
In-Reply-To: <aedffae2-61ad-eb44-c083-e674f736fd96@linux.intel.com>

Hello

On Fri, 2021-06-11 at 20:57 -0700, Mat Martineau wrote:
> I did some tests with connections with checksums enabled, between the 
> export branch and the multipath-tcp.org mptcp_trunk branch (v1 mode).

Thank you for checking!

> When the multipath-tcp.org kernel was listening, the connection would 
> always fall back to TCP when the first data was sent by the upstream 
> kernel. The multipath-tcp.org kernel was the first to fall back and stop 
> sending MPTCP headers.

This sounds like a csum error detected ??! What does wireshark say
about the MPTCP csum value?

> When the upstream kernel was listening, the multipath-tcp.org kernel would 
> send corrupt TCP options with the first data packet (the first time a DSS 
> option was sent). The upstream kernel would then send TCP RST.

How does TCP option look like? Could you please share a short pcap
snippet?

Thanks!

Paolo


  reply	other threads:[~2021-06-14  8:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12  3:57 MPTCP checksum interop Mat Martineau
2021-06-14  8:30 ` Paolo Abeni [this message]
2021-06-15  0:14   ` Mat Martineau

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=8cceb711ad974911da62d62a354e6569b573e0b2.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=geliangtang@gmail.com \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    /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).