Peplink – Load Balancing Algorithms

High Performance Routing for Every Application

Peplink - Load Balancing Algorithms
Peplink – Load Balancing Algorithms

Peplink’s load balancing algorithms help you easily fine-tune how traffic is distributed across connections. Each deployment has a unique setup, and Peplink’s enterprise grade load balancing features can fulfill all of your special requirements. Create your own rule with the following algorithms and you can sit back and enjoy the high performance routing that Peplink brings to you.

Weighted Balance

Assign more traffic to a faster link or less traffic to a connection with a bandwidth cap.

  • Set a weight on the scale for each connection and outgoing traffic will be proportionally distributed according to the specified ratio. (e.g. 1:3:2)
Weighted Balance
Weighted Balance

 

Priority

Route traffic to your preferred link as long as it’s available.

  • Arrange the connection priority order, and traffic will be routed through the healthy link that has the highest priority in the list. Lower priority links will only be used if the current connection fails.
Priority
Priority

 

Overflow

Prevent traffic flow from slowing down when the connection runs out of available bandwidth.

  • 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.
Overflow
Overflow

 

Persistence

Eliminate session termination issue for HTTPS, E-banking, and other secure websites.

  • Specify a traffic type and it will be routed through the same connection persistently based on its source and/or destination IP addresses. Traffic will keep routing on the same connection until the session ends.
Persistence
Persistence

 

Least Used

Help you choose the better connection with more free bandwidth.

  • Traffic will be directed to the link with the most available bandwidth among the selected connections.
Least Used
Least Used

 

Lowest Latency

Give you the fastest response time when using applications like online gaming.

  • Traffic will be assigned to the link with the lowest latency time among the selected connections.
Lowest Latency
Lowest Latency

 

Enforced

Restrict outbound traffic to a particular connection.

  • Select a connection and the specified traffic type will be routed through it at all times, whether the link is up or down.
  • For scenarios like accessing a server that only allows users from a specific IP.
Enforced
Enforced


Example 1 – Setting up Weighted Balance Rules

The basic idea behind Weighted Balance rules is to govern how Peplink Balance distributes outgoing traffic requests across multiple WAN links.

To illustrate, with the following link configuration:

  • WAN1: 3M (DSL)
  • WAN2: 2M (E1)
  • WAN3: 3M (DSL)

The Weighted Balance rule should be set as follows:

  • Service: General
  • Source & Destination IP: Any
  • Protocol & Port: Any
  • Algorithm: Weighted Balance
  • Load Distribution Weight: 3 : 2 : 3 (Derived from 3M : 2M : 3M)

This distributes a larger proportion of traffic to WAN1 and WAN3 to take advantage of the faster links, and a smaller proportion of traffic to WAN2 to prevent over-saturation of the slower link.

Example 2 – Setting up Per-service Weight Balance Rules

Some types of WAN links have different upstream and downstream speeds (e.g. ADSL with 3M upstream and 512K downstream). In such cases, upload-intensive services may require special fine-tuning.

A common example is outgoing email (SMTP), where traffic is mostly upstream.

Building upon the previous link configuration:

  • WAN1: 3M Downstream, 512K Upstream (DSL)
  • WAN2: 2M Downstream, 2M Upstream (E1)
  • WAN3: 3M Downstream, 512K Upstream (DSL)

A per-service Weighted Balance rule should be added for SMTP as follows:

  • Service: SMTP
  • Source & Destination IP: Any
  • Protocol & Port: TCP 25
  • Algorithm: Weighted Balance
  • Load Distribution Weight: 1 : 4 : 1 (Derived from 512K : 2M : 512K)

Example 3 – Restricting IPSec VPN Traffic to the WAN1 Link

To configure Peplink Balance to restrict IPSec VPN traffic to WAN1, add the following per-service Enforced rules:

Rule to specify UDP Port 500 traffic:

  • Service Name: UDP500_on_WAN1
  • Source & Destination IP: Any
  • Protocol & Port: UDP 500
  • Algorithm: Enforced
  • Enforced Connection: WAN1

Rule to specify UDP Port 4500 traffic:

  • Service: UDP4500_on_WAN1
  • Source & Destination IP: Any
  • Protocol & Port: UDP 4500
  • Algorithm: Enforced
  • Enforced Connection: WAN1

With these rules enabled, Peplink Balance will route IPSec VPN traffic with NAT-T (that require UDP ports 500 and 4500) to WAN1 regardless of its up/down status. In the event the WAN1 is down, by design, the specified traffic will simply be dropped rather than routed via the other WAN links.

Reference – 3gig.co.th