Tweet
Peplink routers are true load balancing (link aggregation) routers that offer seamless failover which is different from other multi-wan routers in the market that claim to do load balancing. Note by seamless failover we mean where there's no user intervention required which surprisingly some routers that claim to have failover dont support. In many of the applications that rfwel is involved with in remote areas we truly do need a persistent connection and these Peplink routers are quite impressive!! Here are the load balancing algorithms supported:
• Weighted Balance: The amount of matching traffic that is distributed to a WAN connection is proportional to the weight of the WAN connection relative to the total weight. Use sliders to change the weight for each WAN. You can use prior knowledge of the quality of the WAN or cost of WAN (e.g if you have less allowed usage per month you weight it lower).
• Persistence: With the algorithm Persistence of Pepwave MAX, rules can be configured to enable client computers to persistently utilize the same WAN connections for e-banking and other secure websites where link load distribution might be undesirable for security reasons. As a result, a client computer will communicate with the other end using one IP address and eliminate the risk of host website terminating the session because ip address changed.
• Enforced: specifies the WAN connection usage to be applied on the specified IP Protocol & Port regardless of the connection’s health check status. For example if you have a high bandwidth 4G WiMax or DSL/Cable you might want streaming video to go through that always.
• Priority: specifies the priority of the WAN connections to be utilized 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.
• Least Used: The traffic matching this rule will be routed through the healthy WAN connection that is selected and that has the most available downstream bandwidth.
• Lowest Latency: The traffic matching this rule will be routed through the healthy WAN connection that is selected and that has the lowest latency. Important for latency-critical applications like live video surveillance or VOIP.
• Weighted Balance: The amount of matching traffic that is distributed to a WAN connection is proportional to the weight of the WAN connection relative to the total weight. Use sliders to change the weight for each WAN. You can use prior knowledge of the quality of the WAN or cost of WAN (e.g if you have less allowed usage per month you weight it lower).
• Persistence: With the algorithm Persistence of Pepwave MAX, rules can be configured to enable client computers to persistently utilize the same WAN connections for e-banking and other secure websites where link load distribution might be undesirable for security reasons. As a result, a client computer will communicate with the other end using one IP address and eliminate the risk of host website terminating the session because ip address changed.
• Enforced: specifies the WAN connection usage to be applied on the specified IP Protocol & Port regardless of the connection’s health check status. For example if you have a high bandwidth 4G WiMax or DSL/Cable you might want streaming video to go through that always.
• Priority: specifies the priority of the WAN connections to be utilized 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.
• Least Used: The traffic matching this rule will be routed through the healthy WAN connection that is selected and that has the most available downstream bandwidth.
• Lowest Latency: The traffic matching this rule will be routed through the healthy WAN connection that is selected and that has the lowest latency. Important for latency-critical applications like live video surveillance or VOIP.