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
I didn't look at it in details yet but it is certainly going to do the same job as mptcpd when used with the default addr_adv path-manager and probably the other ones.
Maybe there is something to do there to avoid conflicts? Either tell NM not to look at MPTCP or not start mptcpd if NM is started (maybe a bit too restrictive)?
There is certainly something to look at here.
The text was updated successfully, but these errors were encountered:
Recently, NM 1.40.0 added support for MPTCP.
I didn't look at it in details yet but it is certainly going to do the same job as mptcpd when used with the default
addr_adv
path-manager and probably the other ones.Maybe there is something to do there to avoid conflicts? Either tell NM not to look at MPTCP or not start mptcpd if NM is started (maybe a bit too restrictive)?
There is certainly something to look at here.
The text was updated successfully, but these errors were encountered: