Hey guys… 
I have recently set up a Peplink Balance router to manage a multi-WAN network in my small office. We have three internet connections: one high-speed fiber line, a cable broadband connection, and a 4G LTE backup. While the setup is working, I’m not sure if it’s optimized properly for our use case.
Currently, I’ve configured WAN Load Balancing to distribute traffic across all connections, but we’re still experiencing occasional latency spikes and issues with VoIP calls. I suspect it might have to do with how the traffic rules are set up. I’ve read about features like Outbound Policy, Health Checks, and Bandwidth Reservation, but I’m unsure how to apply them effectively.
Here’s what I’m aiming for:
- Prioritize VoIP and video conferencing traffic for stability and low latency.
- Ensure regular browsing and downloads don’t overwhelm the primary fiber connection.
- Seamlessly failover to LTE if the other connections go down.
I check this: https://forum.peplink.com/t/pepwave-max-hd2-high-availability-setup-with-peplink-balandevops But I have not found any solution. Could anyone guide me about this? Could someone guide me on the best practices or settings to achieve this? If there are specific configurations I should try, I’d greatly appreciate detailed steps or resources.
Thanks in advance!
Respected community member! 
Hi…
A start…
About your WAN (Fiber and cable)
you can do this…
About VoIP, you can do this…
under dashboard > advanced > application
Video? You can do something like VoIP, but be very careful… prioritize video, can be dangerous for VoIP traffic.
Don’t forget to adjust the speed of up and down at wan settings…
upload and download bandwidth.
2 Likes
I think this is the problem. Generally, Fiber WAN is the best, Cable is second best, and LTE is a distant third in terms of bandwidth and latency.
If you go to Advanced / Outbound Policy / Default, you have a range of options:
Algorithm
This field allows you to choose the WAN selection algorithm.
Weighted Balance - Traffic will be proportionally distributed among available connections according to the specified load distribution weight.
Persistence - Traffic coming from the same machine will be persistently routed through the same WAN connection.
Enforced - Traffic will be routed through the specified connection regardless of the connection’s health status.
Priority - Traffic will be routed through the healthy connection that has the highest priority.
Overflow - Traffic will be routed through the healthy WAN connection that has the highest priority and is not in full load. When this connection gets saturated, new sessions will be routed to the next healthy WAN connection that is not in full load.
Least Used - Traffic will be routed through the healthy WAN connection that is selected in the field Connection and has the most available downlink / uplink bandwidth.
Lowest Latency - Latency checking packets will be periodically sent to all selected healthy connections. Latency will then be determined by the response time of the second and third hops. New traffic will then be routed to a healthy connection with the lowest average latency during that detection period.
Fastest Response Time - Traffic will be duplicated and sent to all selected healthy connections. The connection with the earliest response will be used to send all further traffic from the session for the fastest possible response time. If there are any slower responses received from other connection afterwards, they will be discarded. As a result, this algorithm selects the most responsive connection on a per session basis.
Lowest Latency is the default.
It sounds like you are using Weighted Balance?
1 Like
