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
TL;DR: With WAN1+WAN2 (fibers) I can reach almost the full sum of both lines (~245 Mbit/s down, ~37 Mbit/s up) after disabling SQM/autorate/auto-calc and entering manual speeds. Adding WAN3 (mobile, 50–80/12–15, 30 ms latency) is unstable: sometimes higher download peaks, but usually degrades the whole aggregation. Looking for advice on best practices to integrate mobile WANs.
✅ Dual WAN aggregation (WAN1 + WAN2)
WAN1: ~150 Mbit/s down / ~20 Mbit/s up
WAN2: ~100 Mbit/s down / ~17 Mbit/s up
Total capacity: ~250 Mbit/s down / ~37 Mbit/s up
Tunnel: Glorytun UDP
OMR version: 0.63-6.12
After some tuning I can now reach almost the full sum of both lines, both in download and upload.
What worked for me:
Disabled Enable SQM and SQM autorate on both WANs
Disabled Calculate speed
Entered manual bandwidth values, about 10–15% lower than the maximum measured capacity (both down and up)
With these changes I consistently get 220–245 Mbit/s down and 36–37 Mbit/s up, which is very close to the theoretical maximum.
⚠️ Issues with WAN3 (mobile phone via USB–Ethernet)
I tried to add a third WAN using a mobile connection (50–80 Mbit/s down / 12–15 Mbit/s up, ~30 ms latency).
Settings applied:
Force TTL = 65 (to avoid carrier tethering limits)
Disabled SQM, SQM autorate, and Calculate speed (same as WAN1/2)
Tested with different lower manual values for down and up
Results:
Speeds are inconsistent and often degrade overall performance.
Once, with a particular combination, I saw a 325 Mbit/s peak in download, but at the cost of a severely limited upload.
In most other cases WAN3 just adds instability and doesn’t improve the aggregate.
❓ Question
Do you have suggestions on how to best exploit the mobile line within aggregation?
I’d like to keep WAN3 in the mix if possible, especially for its upload, but so far it either:
reduces the overall throughput, or
only shows occasional spikes that are not sustainable.
Any advice on scheduler choice, weighting, or specific tuning tricks for mobile WANs in OMR (with Glorytun UDP) would be greatly appreciated!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
TL;DR: With WAN1+WAN2 (fibers) I can reach almost the full sum of both lines (~245 Mbit/s down, ~37 Mbit/s up) after disabling SQM/autorate/auto-calc and entering manual speeds. Adding WAN3 (mobile, 50–80/12–15, 30 ms latency) is unstable: sometimes higher download peaks, but usually degrades the whole aggregation. Looking for advice on best practices to integrate mobile WANs.
✅ Dual WAN aggregation (WAN1 + WAN2)
After some tuning I can now reach almost the full sum of both lines, both in download and upload.
What worked for me:
With these changes I consistently get 220–245 Mbit/s down and 36–37 Mbit/s up, which is very close to the theoretical maximum.
I tried to add a third WAN using a mobile connection (50–80 Mbit/s down / 12–15 Mbit/s up, ~30 ms latency).
Settings applied:
Results:
❓ Question
Do you have suggestions on how to best exploit the mobile line within aggregation?
I’d like to keep WAN3 in the mix if possible, especially for its upload, but so far it either:
Any advice on scheduler choice, weighting, or specific tuning tricks for mobile WANs in OMR (with Glorytun UDP) would be greatly appreciated!
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions