Differences

This shows you the differences between two versions of the page.

--- basic-network [2024/02/20 17:24] – [WAN(x) Settings] -clarity hogwild
+++ basic-network [2024/02/21 02:19] – [WAN(x) Settings] -clarify Load Balance Weights 1 and 5 hogwild
@@ Line 97: / Line 97: @@
 **Load Balance Weight:   **This option is** **visible only when number of WANs > 1. It can be set between 0 and 256.\\
-{{:pasted:20240219-103900.png}}\\
+{{:pasted:20240219-103900.png}}\\  \\
-It is important when setting up a router in a MultiWAN configuration to understand that this performs load-sharing of the links. Load sharing is performed on a session basis to prevent issues with interactive traffic, such as real-time voice/video, RDP, and so on. To adjust how a specific interface will participate in MultiWAN activities, you set the Load Balancing Weight on each interface. The below examples provide more details.\\  \\ Load Balance Weight: 0\\ Does not actively route traffic but will be automatically enabled if all the other primary interfaces with weight greater than 1 fail for whatever reason. This is commonly used n the so called fail-over scenarios. When an interface with weight 0 is to be auto-enabled it will be assigned a weight of 1. Now let's assume we have 2x WANs, WAN0="weight 0" and WAN1="weight 1". At some point WAN1 fails due to an ISP issue, As soon as the failure is spotted WAN0 will bring itself to life starting to route packets. Later on WAN1 recovers its connectivity and as soon as this is identified by the router (might take seconds to minutes), WAN0 is to go back idling while the traffic is re-router by the resuscitated WAN1. This recovering back to the originally active interface is also known as **preempting** and it's the default (currently not configurable) behavior in FT.\\  \\ Load Balance Weight: 1\\ Any value higher than 0 makes the interface actively routing packets. A weight of 1 doesn't necessarily mean anything by itself as it needs to be compared with other Interfaces load Balance Weight. In a hypothetical scenario when WAN0="weight 0" and WAN1="weight 1", this mean WAN1 is handling 100% of the traffic. \\  \\ Load Balance Weight: 5\\ An interface set with e.g. weight 5 would essentially handle 5 new sessions before any other interface is to be used.\\  \\ In a practical example let's say we have 3 WANs:\\  \\  WAN0 = weight 0\\  WAN1 = weight 1\\  WAN2 = weight 5\\  \\  In this scenario WAN0 is to be used only if both WAN1 and WAN2 are both in failed state (can't route packets). WAN1 will handle the very 1st LAN client new session going through the router, where WAN2 is to handle the 2nd,3d,4th,5th,6th. So what's happens to the 7th? It starts again from WAN1 with 1 session and WAN2 will take care of the next 5 new sessions so 8th,9th,10,11,12th.\\   \\
+When configuring a router in a MultiWAN configuration, the MultiWAN function performs load-sharing of the links. Load sharing is performed on a per-session basis to prevent issues with interactive traffic, such as real-time voice/video, or RDP. Setting the Load Balance Weight on each interface adjusts how that interface will participate in MultiWAN activities. Below are some examples.\\  \\ Load Balance Weight: 0\\ If "0" is used, FreshTomato will not actively route traffic, but the WAN connection with weight "0" will automatically be enabled if all other primary interfaces with weight greater than "1" fail. This is commonly used in "failover" scenarios. When an interface with weight "0" is us auto-enabled, it will be assigned a weight of 1.
+For example:
+Let's assume we have 2x WANs with:
+WAN0="weight 0"
+WAN1="weight 1"
+At some point, WAN1 fails. As soon as this failure is noticed, WAN0 will bring itself to life and begin routing packets. Later, WAN1 recovers its connectivity. As soon as FreshTomato recognizes this, (within seconds or minutes), WAN0 will go back to idle status while traffic is rerouted through the resuscitated WAN1. This recovery, back to the originally active interface is also known as //preempting//.** **Preempting is FreshTomato's default (and fixed) behaviour. c\\  \\ Load Balance Weight: 1\\ Any value higher than "0" causes an interface to actively route packets. A weight of "1" doesn't necessarily mean much by itself. Weights are relative. Each weight is compared to the load balance weights of other Interfaces to direct functionality. If WAN0="weight 0" and WAN1="weight 1", that means WAN1 is handling 100% of the traffic. \\  \\ Load Balance Weight: 5\\ An interface set with e.g. weight 5 would essentially handle 5 new sessions before any other interface is to be used.\\  \\ In a practical example let's say we have 3 WANs:\\  \\  WAN0 = weight 0\\  WAN1 = weight 1\\  WAN2 = weight 5\\  \\ In this case, WAN0 is to be used only if both WAN1 and WAN2 are both in a failed state, and can't route packets. WAN1 will handle the very first 1st LAN client new session going through the router, where WAN2 is to handle the second, third, fourth, fifth and so on. What's happens to the seventh? It starts again from WAN1 with 1 session and WAN2 will take care of the next 5 new sessions so 8th,9th,10,11,12th.\\   \\
 A very important final point on MultiWAN load-sharing: **You can only affect traffic outbound**. This implicitly means that returning traffic will always aim the FT's WAN interface that originated the traffic. As the allocation of new session to a WAN is dynamic, you could control what traffic gets allocated to what Interface (a.k.a. sticky connection) via the [[advanced-pbr|MultiWAN routing]] configuration page.

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools