WAN Balancer FAQs - Revision history

Græmer at 22:04, 14 September 2023

2023-09-14T22:04:37Z

← Older revision		Revision as of 22:04, 14 September 2023
Line 24:		Line 24:


	=== How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism? === 💡		=== How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism? 💡 ===

	Some sites and services use the source/client IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.		Some sites and services use the source/client IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.

	=== How is traffic routed when WAN Balancer is not installed? === 💡		=== How is traffic routed when WAN Balancer is not installed? 💡 ===

	Traffic is routed based on the routing table. If you have multiple WAN interfaces, then multiple default gateways are present in the routing table. In this situation and without WAN Balancer Internet traffic is arbitrarily sent via either link. WAN Balancer enables you to have more control over how Internet traffic should be routed.		Traffic is routed based on the routing table. If you have multiple WAN interfaces, then multiple default gateways are present in the routing table. In this situation and without WAN Balancer Internet traffic is arbitrarily sent via either link. WAN Balancer enables you to have more control over how Internet traffic should be routed.

	=== Is bypassed traffic still routed according to WAN Balancer Route Rules? ===		=== Is bypassed traffic still routed according to WAN Balancer Route Rules? 💡 ===

	Yes. WAN Balancer writes rules directly to iptables. No decisions are made in the UVM, so bypassed traffic is still routed according to those rules.		Yes. WAN Balancer writes rules directly to iptables. No decisions are made in the UVM, so bypassed traffic is still routed according to those rules.

Græmer at 22:04, 14 September 2023

2023-09-14T22:04:17Z

← Older revision		Revision as of 22:04, 14 September 2023
Line 5:		Line 5:


	=== Are the bandwidth settings percentages? === 💡		=== Are the bandwidth settings percentages? 💡 ===

	No - enter bandwidth numbers for each connection that are relative to each other and Untangle will determine the proper percentages. The percentages will be displayed as numbers are entered to help you determine the proper weighting.		No - enter bandwidth numbers for each connection that are relative to each other and Untangle will determine the proper percentages. The percentages will be displayed as numbers are entered to help you determine the proper weighting.

Græmer: /* How is traffic routed when WAN Balancer is not installed? */

2023-09-14T22:03:55Z

How is traffic routed when WAN Balancer is not installed?

← Older revision		Revision as of 22:03, 14 September 2023
Line 28:		Line 28:
	Some sites and services use the source/client IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.		Some sites and services use the source/client IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.

	=== How is traffic routed when WAN Balancer is not installed? ===		=== How is traffic routed when WAN Balancer is not installed? === 💡

	Traffic is routed based on the routing table. If you have multiple WAN interfaces, then multiple default gateways are present in the routing table. In this situation and without WAN Balancer Internet traffic is arbitrarily sent via either link. WAN Balancer enables you to have more control over how Internet traffic should be routed.		Traffic is routed based on the routing table. If you have multiple WAN interfaces, then multiple default gateways are present in the routing table. In this situation and without WAN Balancer Internet traffic is arbitrarily sent via either link. WAN Balancer enables you to have more control over how Internet traffic should be routed.


	=== Is bypassed traffic still routed according to WAN Balancer Route Rules? ===		=== Is bypassed traffic still routed according to WAN Balancer Route Rules? ===

	Yes. WAN Balancer writes rules directly to iptables. No decisions are made in the UVM, so bypassed traffic is still routed according to those rules.		Yes. WAN Balancer writes rules directly to iptables. No decisions are made in the UVM, so bypassed traffic is still routed according to those rules.

Græmer: /* How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism? */

2023-09-14T22:03:49Z

How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism?

← Older revision		Revision as of 22:03, 14 September 2023
Line 24:		Line 24:


	=== How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism? ===		=== How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism? === 💡

	Some sites and services use the source/client IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.		Some sites and services use the source/client IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.


	=== How is traffic routed when WAN Balancer is not installed? ===		=== How is traffic routed when WAN Balancer is not installed? ===

Græmer: /* Are the bandwidth settings percentages? */

2023-09-14T22:03:39Z

Are the bandwidth settings percentages?

← Older revision		Revision as of 22:03, 14 September 2023
Line 5:		Line 5:


	=== Are the bandwidth settings percentages? ===		=== Are the bandwidth settings percentages? === 💡

	No - enter bandwidth numbers for each connection that are relative to each other and Untangle will determine the proper percentages. The percentages will be displayed as numbers are entered to help you determine the proper weighting.

			No - enter bandwidth numbers for each connection that are relative to each other and Untangle will determine the proper percentages. The percentages will be displayed as numbers are entered to help you determine the proper weighting.

	=== Why is some of my internet traffic being stopped? ===		=== Why is some of my internet traffic being stopped? ===

Græmer at 14:01, 14 June 2022

2022-06-14T14:01:09Z

← Older revision		Revision as of 14:01, 14 June 2022
Line 28:		Line 28:

	Some sites and services use the source/client IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.		Some sites and services use the source/client IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.


	=== How is traffic routed when WAN Balancer is not installed? ===		=== How is traffic routed when WAN Balancer is not installed? ===

	Traffic is routed based on the routing table. If you have multiple WAN interfaces, then multiple default gateways are present in the routing table. In this situation and without WAN Balancer Internet traffic is arbitrarily sent via either link. WAN Balancer enables you to have more control over how Internet traffic should be routed.		Traffic is routed based on the routing table. If you have multiple WAN interfaces, then multiple default gateways are present in the routing table. In this situation and without WAN Balancer Internet traffic is arbitrarily sent via either link. WAN Balancer enables you to have more control over how Internet traffic should be routed.


	=== Is bypassed traffic still routed according to WAN Balancer Route Rules? ===		=== Is bypassed traffic still routed according to WAN Balancer Route Rules? ===

	Yes. WAN Balancer writes rules directly to iptables. No decisions are made in the UVM, so bypassed traffic is still routed according to those rules.		Yes. WAN Balancer writes rules directly to iptables. No decisions are made in the UVM, so bypassed traffic is still routed according to those rules.

Græmer at 14:00, 14 June 2022

2022-06-14T14:00:47Z

← Older revision		Revision as of 14:00, 14 June 2022
Line 31:		Line 31:
	=== How is traffic routed when WAN Balancer is not installed? ===		=== How is traffic routed when WAN Balancer is not installed? ===
	Traffic is routed based on the routing table. If you have multiple WAN interfaces, then multiple default gateways are present in the routing table. In this situation and without WAN Balancer Internet traffic is arbitrarily sent via either link. WAN Balancer enables you to have more control over how Internet traffic should be routed.		Traffic is routed based on the routing table. If you have multiple WAN interfaces, then multiple default gateways are present in the routing table. In this situation and without WAN Balancer Internet traffic is arbitrarily sent via either link. WAN Balancer enables you to have more control over how Internet traffic should be routed.

			=== Is bypassed traffic still routed according to WAN Balancer Route Rules? ===
			Yes. WAN Balancer writes rules directly to iptables. No decisions are made in the UVM, so bypassed traffic is still routed according to those rules.

Bcarmichael: /* How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism? */

2020-09-03T14:28:35Z

How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism?

← Older revision		Revision as of 14:28, 3 September 2020
Line 28:		Line 28:

	Some sites and services use the source/client IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.		Some sites and services use the source/client IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.

			=== How is traffic routed when WAN Balancer is not installed? ===
			Traffic is routed based on the routing table. If you have multiple WAN interfaces, then multiple default gateways are present in the routing table. In this situation and without WAN Balancer Internet traffic is arbitrarily sent via either link. WAN Balancer enables you to have more control over how Internet traffic should be routed.

Dmorris: /* How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism? */

2017-11-21T17:52:40Z

How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism?

← Older revision		Revision as of 17:52, 21 November 2017
Line 27:		Line 27:
	=== How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism? ===		=== How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism? ===

	Some sites and services ~~(incorrectly)~~ use the source IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.		Some sites and services use the source/client IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.

Dmorris at 16:26, 21 November 2017

2017-11-21T16:26:04Z

← Older revision		Revision as of 16:26, 21 November 2017
Line 23:		Line 23:

	No. A bonded connection combines the bandwidth of multiple internet connections from a single ISP into a single physical connection, often requiring additional hardware at each end of the connection.		No. A bonded connection combines the bandwidth of multiple internet connections from a single ISP into a single physical connection, often requiring additional hardware at each end of the connection.


			=== How does WAN Balancer handle services that use the IP as the primary key or authentication mechanism? ===

			Some sites and services (incorrectly) use the source IP to identify users which can cause issue if the service uses multiple sessions as when balancing across several WANs subsequent sessions could exit another WAN and thus us a different source IP. To avoid these type of issues all sessions that are randomly assigned a WAN based on the weights (balanced) will continue to use the same WAN for all connections between a given internal IP and external IP. In other words, all sessions between A and B are sticky to a specific WAN.