There are two persistent modes: By Source and By Destination.
The same WAN connection will be used for traffic matching the rule and
originating from the same machine, regardless of its destination. This option
will provide the highest level of application compatibility.
The same WAN connection will be used for traffic matching the rule,
originating from the same machine, and going to the same destination. This
option can better distribute loads to WAN connections when there are only a
few client machines.
The default mode is By Source. When there are multiple client requests, they can be distributed
(persistently) to WAN connections with a weight. If you choose Auto in Load Distribution, the
weights will be automatically adjusted according to each WAN’s Downstream Bandwidth which
is specified in the WAN settings page). If you choose Custom, you can customize the weight of
each WAN manually by using the sliders.
12.1.3 Algorithm: Enforced
This setting specifies the WAN connection usage to be applied on the specified IP protocol and
port. This setting is applicable only when Algorithm is set to Enforced.
Matching traffic will be routed through the specified WAN connection, regardless of the health
check status of the WAN connection. Starting from Firmware 5.2, outbound traffic can be
enforced to go through a specified SpeedFusion
TM
connection.
12.1.4 Algorithm: Priority
This setting specifies the priority of the WAN connections used to route the specified network
service. The highest priority WAN connection available will always be used for routing the
specified type of traffic. A lower priority WAN connection will be used only when all higher
priority connections have become unavailable.
To Next Page
Loading...
Need help?
General
