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/20 19:13] – [WAN(x) Settings] -clarity, condense of WAN load weight hogwild | ||
---|---|---|---|
Line 93: | Line 93: | ||
\\ | \\ | ||
- | **Load Balance Weight: | + | \\ |
+ | |||
+ | **Load Balance Weight: | ||
{{: | {{: | ||
- | A very important concept to digest when setting up your device | + | When configuring a router |
- | \\ | + | |
- | Load Balance Weight: 0\\ | + | Now, let's assume we have 2x WANs: |
- | Does not actively route traffic but will be automatically | + | |
- | \\ | + | WAN0=" |
- | Load Balance Weight: 1\\ | + | |
- | Any value higher than 0 makes the interface actively | + | WAN1=" |
- | \\ | + | |
- | Load Balance Weight: 5\\ | + | At some point, WAN1 fails. As soon as the failure is noticed, |
- | 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 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: | A very important final point on MultiWAN load-sharing: |