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 [2023/11/28 09:36] – Group Key Renewal - update for limits with 2023.5 and up m_ars | basic-network [2024/02/21 17:54] – [WAN(x) Settings] -clarify Load Balance Weight and add OOO explanation hogwild | ||
---|---|---|---|
Line 92: | Line 92: | ||
\\ | \\ | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **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 387: | 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] | ||
Line 510: | Line 524: | ||
**Group Key Renewal: | **Group Key Renewal: | ||
- | (Default: 3600 seconds). | + | (Default: 3600 seconds). |