All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>,
	 Geliang Tang <geliangtang@gmail.com>,
	Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: MPTCP checksum interop
Date: Fri, 11 Jun 2021 20:57:11 -0700 (PDT)	[thread overview]
Message-ID: <aedffae2-61ad-eb44-c083-e674f736fd96@linux.intel.com> (raw)


I did some tests with connections with checksums enabled, between the 
export branch and the multipath-tcp.org mptcp_trunk branch (v1 mode).

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.

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.

The initial impression is that there are some issues with mptcp_trunk and 
checksums - I did not have time today to look at packet captures between 
two mptcp_trunk kernels.

These results were the same when only one side of the connection had 
checksums enabled, or if both kernels did.

I haven't narrowed down the cause, but will do some more experiments on 
Monday.

--
Mat Martineau
Intel

             reply	other threads:[~2021-06-12  3:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12  3:57 Mat Martineau [this message]
2021-06-14  8:30 ` MPTCP checksum interop Paolo Abeni
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=aedffae2-61ad-eb44-c083-e674f736fd96@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=geliangtang@gmail.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.