-
-
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
A hypothesis #478
Comments
Hi, Similar to the |
Please ask questions in English, this is a good opportunity for you to practice your English. Next time, I will simply ignore questions like this. Even if you ask it in Chinese, your description of the question is very inaccurate, giving me a feeling that you are very casual. We are all developers of MPTCP, and we expect to answer those accurate questions from serious questioners. We hope that the questioners have a basic understanding of MPTCP and have at least read the WIKI page. [1] Now back to your question, "A hypothesis". The first question is about switching between TCP and MPTCP. I don't understand your intention, but the general answer is: Establishing an MPTCP connection requires three handshakes, just like TCP. If the handshake fails, it will fall back to a TCP connection. [2] Legacy TCP applications can switch to MPTCP through the mptcpize tool or BPF. [3] The second question is about so-called "multipath UDP", please refer to mp-dccp. We do not intend to discuss it here. [4] [1] https://github.com/multipath-tcp/mptcp_net-next/wiki |
Hello I guess it is fine to close this ticket, right? I think @geliangtang replied to all questions (thanks!). |
Edited by @matttbe:
Translation from Google:
Can you provide a detection mechanism that automatically switches to the mptcp protocol when the host network reaches the peer with multiple exits? It degrades to traditional tcp when the host network has only a single exit. In addition, can UDP realize functions similar to MPTCP?
The text was updated successfully, but these errors were encountered: