search

multipath-tcp / mptcp

⚠️⚠️⚠️ Deprecated 🚫 Out-of-tree Linux Kernel implementation of MultiPath TCP. 👉 Use https://github.com/multipath-tcp/mptcp_net-next repo instead ⚠️⚠️⚠️
https://github.com/multipath-tcp/mptcp_net-next
Other
889 stars 335 forks source link

Classes of Interfaces, Price of Interface, Maximum parralel Streams ... #26

Open arrrgrr opened 10 years ago

arrrgrr commented 10 years ago

There must be the possibility to classify the Interfaces. MPTCP than musts only transport the interfaces of the same class to the opposite side. Why is this essential? In case of VPN you dont want to leave the Private Area in case of MPTCP over VPN. In case of VPN over MPTCP you want to avoid putting Data of the VPN in the VPN which creates double escapes and increased latency.

Also i prefer a value like Maximum TCP channels in the /proc/sys/net/mpctcp Assuming your client have n IPv6 ans your Server m IPv6, the Kernel Creates n*m full Mesch .... this consumes a lot of Storage.

A great Deal may be the possibility to configure to prefer some Interfaces, because of the option to make a combination of Expansive Flat Rate and Cheep Volume ISP in redundant VPN Networks

gdetal commented 10 years ago

Hi,

I don't see the interest of classifying the interfaces. Maybe I didn't understand your use case with VPNs...

For the latest point, there is a mechanism to avoid using an interface if another one is available. This does not increase the throughput but provides redundancy which seems to be what you are looking for. See http://multipath-tcp.org/pmwiki.php/Users/Tools for more infos.