Hi Matthieu,

So, MPTCP flow doesn't work if client is installed with MPTCP V1 and server with MPTCP V0? In this case, Client falls back to TCP in initial handshake itself?


Thanks,
Sandeep.


On Thu, 15 Oct 2020, 2:00 pm Matthieu Baerts <matthieu.baerts@tessares.net wrote:
Hi Yoshi,

On 15/10/2020 10:09, yoshi nishida wrote:
> Hmm. I've tried v0.95 mptcp kernel and kernel5.8 on ubuntu20.10.
> I tried both version 0 and 1 on v.95, but didn't work. But, I might
> miss something.

I guess you are referring to a sysctl parameter, right? If yes, on
v0.95, there is a partial support of MPTCPv1 regarding the modifications
around ADD_ADDR (with or without HMAC I think) but that's it.

The v0.95 doesn't support the new way of initiating an MPTCP connection
making v0 and v1 incompatible. Of course, except if a fallback from v1
to v0 is implemented, which is not the case in the upstream version.

But in other words, v0.95 is not compatible with MPTCPv1. Only
mptcp_trunk is:

https://github.com/multipath-tcp/mptcp/tree/mptcp_trunk

> I will dig into this a bit more as well as some minor issues I noticed
> during the weekend.

Thanks!

Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
_______________________________________________
mptcp mailing list -- mptcp@lists.01.org
To unsubscribe send an email to mptcp-leave@lists.01.org