WAN Balancer - Revision history

Dmorris at 18:15, 20 June 2018

2018-06-20T18:15:17Z

← Older revision		Revision as of 18:15, 20 June 2018
Line 7:		Line 7:
	{\| width='100%'		{\| width='100%'
	\|-		\|-
	\| align="center" \| [[Image:~~WANBalancer_128x128~~.png]]     '''WAN Balancer'''		\| align="center" \| [[Image:WANBalancer.png\|128px]]     '''WAN Balancer'''
	\| align="center" \|		\| align="center" \|
	{\|		{\|

Dmorris at 21:44, 14 June 2017

2017-06-14T21:44:33Z

← Older revision		Revision as of 21:44, 14 June 2017
Line 15:		Line 15:
	\|[http://www.untangle.com/store/wan-balancer-conf.html WAN Balancer Description Page]		\|[http://www.untangle.com/store/wan-balancer-conf.html WAN Balancer Description Page]
	\|-		\|-
	\|[http://~~www~~.untangle.com/~~videos~~/ WAN Balancer ~~Video~~ Demo]		\|[http://demo.untangle.com/admin/index.do#service/wan-balancer WAN Balancer Demo]
	\|-		\|-
	\|[http://forums.untangle.com/wan-balancer/ WAN Balancer Forums]		\|[http://forums.untangle.com/wan-balancer/ WAN Balancer Forums]

Dmorris at 17:30, 12 June 2017

2017-06-12T17:30:27Z

← Older revision		Revision as of 17:30, 12 June 2017
Line 55:		Line 55:
	If there is no route in the cache, then a WAN will be chosen based on the hash of the source and destination and the weights given in the ''Traffic Allocation'' settings. Not that the traffic allocation weights don't determine exactly the percentages of traffic over the various WANs, only how sessions will be assigned to various WANs.		If there is no route in the cache, then a WAN will be chosen based on the hash of the source and destination and the weights given in the ''Traffic Allocation'' settings. Not that the traffic allocation weights don't determine exactly the percentages of traffic over the various WANs, only how sessions will be assigned to various WANs.

			{{ServiceAppScreenshot\|wan-balancer\|traffic-allocation}}
	----


Line 77:		Line 76:
	''Note:'' [[Routes]] and routes based on the network configuration always override Route Rules. Route Rules only apply to sessions that have no local route based on configuration on routes in [[Routes]]. Route Rules are basically a suggestion that the traffic be routed out a specific WAN if no other route says where to send it.		''Note:'' [[Routes]] and routes based on the network configuration always override Route Rules. Route Rules only apply to sessions that have no local route based on configuration on routes in [[Routes]]. Route Rules are basically a suggestion that the traffic be routed out a specific WAN if no other route says where to send it.
	</blockquote>		</blockquote>

			{{ServiceAppScreenshot\|wan-balancer\|route-rules}}

Dmorris at 17:15, 12 June 2017

2017-06-12T17:15:38Z

← Older revision		Revision as of 17:15, 12 June 2017
Line 44:		Line 44:
	This tab displays information and statistics for each WAN interface.		This tab displays information and statistics for each WAN interface.

			{{ServiceAppScreenshot\|wan-balancer\|status}}
	~~---~~-

Dmorris at 15:58, 17 July 2016

2016-07-17T15:58:05Z

New page

[[Category:Applications]]
WAN_Balancer
WAN_Balancer#Status
WAN_Balancer#Traffic_Allocation
WAN_Balancer#Route_Rules

{| width='100%'
|-
| align="center" | [[Image:WANBalancer_128x128.png]]     '''WAN Balancer'''
| align="center" |
{|
|-
| Other Links:
|-
|[http://www.untangle.com/store/wan-balancer-conf.html WAN Balancer Description Page]
|-
|[http://www.untangle.com/videos/ WAN Balancer Video Demo]
|-
|[http://forums.untangle.com/wan-balancer/ WAN Balancer Forums]
|-
|[[WAN Balancer Reports]]
|-
|[[WAN Balancer FAQs]]
|}
|}
 
----

== About WAN Balancer ==

WAN Balancer works in conjunction with multiple ISPs to distribute your traffic across multiple connections. It will decide dynamically which WAN connection to send traffic over, maximizing your bandwidth usage.

You may also consider using [[WAN Failover]] in your network as well - it automatically reroutes traffic over working WAN links when one fails. If [[WAN Failover]] is running and detects a WAN as being down WAN Balancer will not balance traffic to that WAN.

== Settings ==

This section reviews the different settings and configuration options available for WAN Balancer.

=== Status ===

This tab displays information and statistics for each WAN interface.

----

=== Traffic Allocation ===

On the '''Traffic Allocation''' tab, you set the weighs for each WAN connection. If you only have one WAN defined, you will only see one interface listed here. Simply enter the weighting you desire, check that you are good with the percentages assigned to each WAN, and hit save.

As each WAN Balancer processes each new session it decides which WAN it will use to send this traffic if there is no local route for the traffic. If traffic between these two IPs has taken place recently then there is likely a route already in the cache. If so, this route will be used to send this new session. This is to assure that all traffic between two IPs uses the same WAN consistently to avoid issues with cloud services.

If there is no route in the cache, then a WAN will be chosen based on the hash of the source and destination and the weights given in the ''Traffic Allocation'' settings. Not that the traffic allocation weights don't determine exactly the percentages of traffic over the various WANs, only how sessions will be assigned to various WANs.

----

=== Route Rules ===

''Route Rules'' determine which WAN will be used for traffic going to the internet (traffic with no local route). As described in the [[Rules|rules documentation]], the ''Route Rules'' are evaluated in order for new sessions and the first matching rule will determine which WAN interface is used. If no matching rule is found or the first matching rule has a ''Destination WAN'' set to ''Balance'' then the session will be randomly assigned a route based on ''Traffic Allocation'' settings. A limited set of conditions are available to WAN Balancer Route Rules which include source, destination, port and protocol.

This allows you to specify which WAN is used for certain traffic based on a variety of conditions. For example:
* To put all one server's traffic on a specific WAN add a rule with condition "''Source Address'' is server_ip" and the ''Destination WAN'' is the WAN to be used.
* To put all SMTP to go out a specific WAN, add a rule with "''Destination Port'' is 25" and the ''Destination WAN'' is the WAN to be used.

This can also be useful if you have one connection with less throughput but lower latency. In this case you can specify that all VOIP or latency sensitive traffic use the lower latency connection.

<blockquote>
''Note:'' Unlike [[Routes]], Route Rules that route traffic to a WAN that is down will automatically balance traffic to one of the active WANs. For example, if a rule says to send all port 25 traffic to WAN2, but [[WAN Failover]] knows WAN2 is down, this rule will effectively mean ''Balance'' which means the session will be put on one of the other active WANs.
</blockquote>

<blockquote>
''Note:'' [[Routes]] and routes based on the network configuration always override Route Rules. Route Rules only apply to sessions that have no local route based on configuration on routes in [[Routes]]. Route Rules are basically a suggestion that the traffic be routed out a specific WAN if no other route says where to send it.
</blockquote>

== Reports ==

{{:WAN Balancer Reports}}

== Related Topics ==

* [[WAN Failover|WAN Failover]]

== WAN Balancer FAQs ==

{{:WAN Balancer FAQs}}