Based on the understand of Overflow method. It is Drag and drop to arrange the connection overflow order and the highest priority link will route traffic as long as it has not been congested. Once it saturates, the lower priority links will start routing traffic.
Scenario:
My network environment has two network connection connected to Peplink perspective:
WAN1: 1mbps
WAN2: 4mbps
At this same time WAN1 AND WAN2 fully congestion. Then possible the policy set at 1) remaining using the WAN2 is a priority for route the traffic or else?
Outbound policy are top → down approach. Seem the same outbound policy ( source=any destination=xx.xx.xx.xx protocol/port=any) criteria is defined, second overflow policy is useless.
@Yeoh Can you put in your concerns here regarding the defined outbound policies ? Why you need to defined such policies ? What you need to achieve here ?
In production environment for overflow algorithm, you will see that the new connections for destination 103.123.20.10 will assigned to WAN1 / WAN2 base on condition usage for WAN1. If both WANs are congested all the times, this is an unhealthy environment and you should not use overflow. Please consider least used algorithm and this should give you better load balance method.
