-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
How OMR works? #3358
Comments
That's a bit simplistic - how it routes is going to be dependent on your settings of whether you optimize for latency or bandwidth etc. If you choose "Enable TCP Low Latency" then it will try to route based on lowest latency. Other things will play a role in routing such as (but not limited to):
|
For kernel 5.4 MPTCP version used: https://www.multipath-tcp.org/ (used in legacy version of OpenMPTCProuter) |
And for OMR, which policy did you choose to work with it? How can I view that when using it? |
|
Yes, that's clear. For the kernel 6.1, how did you configure MPTCP for OMR? Did you choose to prioritize the lowest latency? |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Hello,
I have a question about how OMR works. OMR utilizes MPTCP for aggregation, creating a subflow TCP for each link and primarily sending data through the link with the lowest latency, correct? So, how does this process work exactly? For instance, if you have 10 packets and 3 links, will OMR send 6 packets through the link with the minimum latency and 2 packets through each of the other two links? Is that correct?
The text was updated successfully, but these errors were encountered: