-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support of ndiffport #280
Comments
Hi @hansomesong The current implementation doesn't support ndiffport as the one present in the out-of-tree implementations where the clients create additional sublfows on a different without any interaction with the end server. But it is possible to get something similar with the new MPTCP Upstream implementation:
Please note that on the server side, an additional listening socket might need to be created to accept new subflows on a different port, see issue #203. Please report any issues if this is not working as expected.
Small side note: MPTCPv1 is the protocol, not the Linux implementation ;-) |
Hi @hansomesong Do you mind if I close this story? Do not hesitate to create a PR or an issue to have "ndiffport" support in mptcpd. |
Mat is currently working on a ndiffports plugin for mptcpd. See multipath-tcp/mptcpd#248. |
Hi Folks,
I would like to know if the upstream implementation of MPTCP supports ndiffport mode, in which we can set up a series of different subflows specified by ndiffport, across the same pair of ip address between end hosts. The motivation behind this question is that we would like to leverage the power of SDN, allocating n different transmission paths between a pair of single-homed end hosts.
If ndiffport feature is supported, how to configure this parameter with MPTCPv1 implementation?
Thanks for any feedback in advance.
The text was updated successfully, but these errors were encountered: