Skip to content
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.

MPTCP is not recreating the broken subflows after a connection drop on that WAN. #521

Open
vempire-ghost opened this issue Jan 20, 2024 · 2 comments

Comments

@vempire-ghost
Copy link

Hello, I'm using MPTCP with the redundant scheduler. However, every time a WAN experiences an internet outage, and its subflows stop carrying data, when the internet comes back, none of the subflows resume data traffic, no matter how much time passes.

However, in this demonstration, as soon as the connection is restored, the data starts flowing again. I would like to understand why this is not happening in my system.
https://www.youtube.com/watch?v=VWN0ctPi5cw

Even with this option /sys/module/mptcp_fullmesh/parameters/create_on_err set to 1, whenever a connection is deactivated and reactivated, the traffic does not resume. The only way to make the data flow again on that WAN is to use 'multipath eth off,' wait for at least 1 second, and 'multipath eth on.' At that moment, all data starts flowing through all subflows that were previously without traffic.
However, this is not an ideal solution; it would be preferable if, upon returning online, the WAN's subflows were automatically reactivated if possible. Thank you very much for the work done on this project.

@vandit86
Copy link

Its a path management problem.

@vempire-ghost
Copy link
Author

Its a path management problem.

And is there any way to solve this issue?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants