[MPTCP] Re: [mptcp-dev] mptcp code in kernel 5.8

[MPTCP] Re: [mptcp-dev] mptcp code in kernel 5.8

[Matthieu Baerts]

[-- Attachment #1: Type: text/plain, Size: 558 bytes --]

Hi Sandeep,

On 20/10/2020 16:19, Sandeep Irlanki wrote:
> 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?

Yes, that's correct.

This could work if the client was able to do a fallback to MPTCP v0 but 
the upstream implementation doesn't support v0 mainly because this 
version was recently deprecated and to simplify the code and maintenance.

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

[MPTCP] Re: [mptcp-dev] mptcp code in kernel 5.8

[Sandeep Irlanki]

[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

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(a)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(a)lists.01.org
> To unsubscribe send an email to mptcp-leave(a)lists.01.org
>

[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 2288 bytes --]

[MPTCP] Re: [mptcp-dev] mptcp code in kernel 5.8

[yoshi nishida]

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

Hi Matt,

I see. Sorry for my misunderstanding and thank you so much for the
clarification!
--
Yoshi

On Thu, Oct 15, 2020 at 1:30 AM Matthieu Baerts
<matthieu.baerts(a)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] Re: [mptcp-dev] mptcp code in kernel 5.8

[Matthieu Baerts]

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

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] Re: [mptcp-dev] mptcp code in kernel 5.8

[yoshi nishida]

[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]

Hi Matt,

Thanks for the reply.
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 will dig into this a bit more as well as some minor issues I noticed
during the weekend.

Thank you so much!
--
Yoshi

On Wed, Oct 14, 2020 at 2:13 AM Matthieu Baerts
<matthieu.baerts(a)tessares.net> wrote:
>
> Hi Yoshi,
>
> On 14/10/2020 11:02, yoshi nishida wrote:
> > Hi Christoph,
> >
> > Sorry for the late reply. Yes, I meant the repo of multipath-tcp.org kernel.
> > As far as I tested, it seems that they are quite different and they
> > cannot interact with each other.
>
> The upstream version only supports the latest MPTCP protocol: v1. All
> stable versions of the multipath-tcp.org kernel only support the now
> deprecated MPTCPv0 protocol. The development version starts supporting
> MPTCPv1.
>
> I guess you likely tested two implementations only supporting 2
> different versions of the protocols that are incompatible with each others.
>
> Please see this for more details:
>
>
> https://github.com/multipath-tcp/mptcp_net-next/wiki#upstream-vs-out-of-tree-implementations
>
> > But, at least, I understand the situation. Thanks for the explanation!
> > So, if I find a bug in the upstream code, it is ok to send it to the
> > upstreaming list?
>
> Yes please, this version is in development so any feedback is welcome!
>
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net

[MPTCP] Re: [mptcp-dev] mptcp code in kernel 5.8

[Matthieu Baerts]

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

Hi Yoshi,

On 14/10/2020 11:02, yoshi nishida wrote:
> Hi Christoph,
> 
> Sorry for the late reply. Yes, I meant the repo of multipath-tcp.org kernel.
> As far as I tested, it seems that they are quite different and they
> cannot interact with each other.

The upstream version only supports the latest MPTCP protocol: v1. All 
stable versions of the multipath-tcp.org kernel only support the now 
deprecated MPTCPv0 protocol. The development version starts supporting 
MPTCPv1.

I guess you likely tested two implementations only supporting 2 
different versions of the protocols that are incompatible with each others.

Please see this for more details:

 
https://github.com/multipath-tcp/mptcp_net-next/wiki#upstream-vs-out-of-tree-implementations

> But, at least, I understand the situation. Thanks for the explanation!
> So, if I find a bug in the upstream code, it is ok to send it to the
> upstreaming list?

Yes please, this version is in development so any feedback is welcome!

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

[MPTCP] Re: [mptcp-dev] mptcp code in kernel 5.8

[yoshi nishida]

[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]

Hi Christoph,

Sorry for the late reply. Yes, I meant the repo of multipath-tcp.org kernel.
As far as I tested, it seems that they are quite different and they
cannot interact with each other.
But, at least, I understand the situation. Thanks for the explanation!
So, if I find a bug in the upstream code, it is ok to send it to the
upstreaming list?

Thanks,
--
Yoshi

On Thu, Oct 8, 2020 at 11:28 AM Christoph Paasch <cpaasch(a)apple.com> wrote:
>
> +MPTCP upstreaming list
>
> Hello Yoshi,
>
> On 10/08/20 - 01:44, yoshi nishida wrote:
> > Hello,
> >
> > It's really great to see mptcp codes in main stream.  So, I've tried
> > to use it with kernel 5.8 in ubuntu20.10.
> > However, as far as I've checked, the mptcp in the kernel seems to be
> > different from the one in the repo.
>
> The repo, you mean the repo of multipath-tcp.org kernel? Yes, they are
> entirely different. The MPTCP implementation in upstream Linux (5.6+) is a
> complete rewrite.
>
> > I am not sure how to set scheduler
> > or path manager with this.
>
> It is currently not possible to select different schedulers on the upstream
> implementation.
>
> For path-management there is an ip-mptcp interface that allows you to add
> subflows and addresses: https://man7.org/linux/man-pages/man8/ip-mptcp.8.html
>
>
> Christoph
>
> > Does anyone know about the differences?
> > Sorry if I overlooked something.
> >
> > Thanks,
> > --
> > Yoshi
>
> > MPTCP-developpers Mailing-List
> > Visit http://multipath-tcp.org to access the source-code of MPTCP in the Linux Kernel
> >
> > To Unsubscribe, visit https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev
> >
>

[MPTCP] Re: [mptcp-dev] mptcp code in kernel 5.8

[Christoph Paasch]

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

+MPTCP upstreaming list

Hello Yoshi,

On 10/08/20 - 01:44, yoshi nishida wrote:
> Hello,
> 
> It's really great to see mptcp codes in main stream.  So, I've tried
> to use it with kernel 5.8 in ubuntu20.10.
> However, as far as I've checked, the mptcp in the kernel seems to be
> different from the one in the repo.

The repo, you mean the repo of multipath-tcp.org kernel? Yes, they are
entirely different. The MPTCP implementation in upstream Linux (5.6+) is a
complete rewrite.

> I am not sure how to set scheduler
> or path manager with this.

It is currently not possible to select different schedulers on the upstream
implementation.

For path-management there is an ip-mptcp interface that allows you to add
subflows and addresses: https://man7.org/linux/man-pages/man8/ip-mptcp.8.html


Christoph

> Does anyone know about the differences?
> Sorry if I overlooked something.
> 
> Thanks,
> --
> Yoshi

> MPTCP-developpers Mailing-List
> Visit http://multipath-tcp.org to access the source-code of MPTCP in the Linux Kernel
> 
> To Unsubscribe, visit https://listes-2.sipr.ucl.ac.be/sympa/info/mptcp-dev
>