Differences

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

--- basic-network [2024/02/21 02:19] – [WAN(x) Settings] -clarify Load Balance Weights 1 and 5 hogwild
+++ basic-network [2024/02/21 02:27] – [WAN(x) Settings] -clarity-load balance weight limitations hogwild
@@ Line 109: / Line 109: @@
 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.\\   \\
+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.\\  \\ For example, say we have 3 WANs, as follows:\\  \\  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.\\   \\ An important final point on MultiWAN load-sharing: **These settings only affect outbound traffic**. Returning traffic will always try to return to the WAN interface from which the traffic originated. 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.
-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