This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
basic-network [2024/02/19 10:43] – [WAN(x) Settings] rs232 | basic-network [2024/02/21 02:27] – [WAN(x) Settings] -clarity-load balance weight limitations hogwild | ||
---|---|---|---|
Line 93: | Line 93: | ||
\\ | \\ | ||
- | **Load Balance Weight: | + | \\ |
- | {{:pasted: | + | **Load Balance Weight: **This option is** **visible only when number of WANs > 1. It can be set between 0 and 256.\\ |
- | A very important concept to digest when setting up your device | + | {{: |
- | \\ | + | |
- | Load Balance Weight: 0\\ | + | When configuring a router |
- | 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 in the so called fail-over | + | |
- | \\ | + | For example: |
- | Load Balance Weight: 1\\ | + | |
- | Any value higher than 0 makes the interface actively routing packets. A weight of 1 doesn' | + | Let's assume we have 2x WANs with: |
- | \\ | + | |
- | Load Balance Weight: 5\\ | + | WAN0=" |
- | An interface set with e.g. weight 5 would essentially handle 5 new sessions before any other interface is to be used.\\ | + | |
- | \\ | + | WAN1=" |
- | In a practical example let's say we have 3WANs:\\ | + | |
- | \\ | + | |
- | 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, | + | |
- | \\ | + | |
- | A very important final point on MultiWAN load-sharing: | + | 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 // |
\\ | \\ |