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:18] – [WAN(x) Settings] rs232 | basic-network [2024/02/21 17:54] – [WAN(x) Settings] -clarify Load Balance Weight and add OOO explanation hogwild | ||
---|---|---|---|
Line 93: | Line 93: | ||
\\ | \\ | ||
- | **Load Balance Weight: | ||
- | |||
- | A very important concept to digest when setting up your device in MultiWAN is the fact that this is a load-sharing of links. A load share is intentionally performed on a session basis this is to prevent issues with interactive traffic like real-time voice/ | ||
- | \\ | ||
- | 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 in 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=" | ||
- | \\ | ||
- | Load Balance Weight: 1\\ | ||
- | Any value higher than 0 makes the interface actively routing packets. A weight of 1 doesn' | ||
- | \\ | ||
- | 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 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 | + | **Load Balance Weight: |
+ | |||
+ | {{: | ||
+ | |||
+ | When configuring a router in a MultiWAN configuration, | ||
+ | |||
+ | For example: | ||
+ | |||
+ | Let's assume we have 2 WANs, as follows: | ||
+ | |||
+ | WAN0=" | ||
+ | |||
+ | WAN1=" | ||
+ | |||
+ | At some point, WAN1 fails. As soon as this failure is noticed, WAN0 will activate (assigned with weight 1) and begin routing packets. Later, WAN1 recovers its connectivity. As soon as FreshTomato recognizes this, (within seconds or minutes), WAN0 will be set back to idle status while traffic is rerouted through the revived WAN1. This process of recovering back to the originally active interface is called // | ||
\\ | \\ | ||
Line 411: | Line 405: | ||
* This is usually only for advanced users. \\ \\ | * This is usually only for advanced users. \\ \\ | ||
- | **Shared Key: | + | **Shared Key: |
- | + | ||
- | **Group Key Renewal: | + | |
- | Starting with release 2023.5 | + | **Group Key Renewal: |
- | 1 sec up to 2592000 sec [for mips RT-N / mips-RT-AC and all ARM routers] | + | |
- | 0 => disabled | + | |
- | Releases up to 2023.4 can adjust | + | Starting with release |
- | 60 sec up to 7200 sec [all routers] | + | |
+ | In releases up to 2023.4, you can set this within the following limits: 60 sec to 7200 sec [all routers] | ||