-
-
Notifications
You must be signed in to change notification settings - Fork 252
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
understanding OMR #3191
Comments
For UDP, by default a VPN over TCP is used and aggregated. Some proxy also can do UDP over TCP (V2Ray and XRay). There is Glorytun UDP and MLVPN as VPN that can aggregate UDP over UDP, but performance and stability is often not really good. |
So if I understand correctly, on the OMR side, MPTCP is used to aggregate both TCP traffic and UDP (VPN over TCP, where VPN options include openVPN TCP and Glorytun TCP). Between OMR and the VPS, shadowsocks is used for TCP, and the same VPN is used for aggregation for UDP, correct? |
yes |
Hello Ysurac, |
The proxy is used for TCP between OMR and the VPS and is encrypted. |
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 am new to this project and eager to understand more about the functionalities of OMR. As far as I've grasped, OMR utilizes MPTCP to aggregate throughput for TCP traffic. However, I'm curious about the handling of UDP traffic. Could you please clarify what method is employed for UDP traffic? I've noticed that openVPN TCP is utilized. Additionally, following the aggregation process, what technology is used for the creation of the tunnel between OMR and VPS to pass the aggregated throughput? Also, could you explain when you use shadowsocks and VPN?
The text was updated successfully, but these errors were encountered: