You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: