This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
basic-network [2024/02/20 17:36] – [WAN(x) Settings] -clarity, condense hogwild | basic-network [2024/02/21 17:54] (current) – [WAN(x) Settings] -clarify Load Balance Weight and add OOO explanation hogwild | ||
---|---|---|---|
Line 97: | Line 97: | ||
**Load Balance Weight: | **Load Balance Weight: | ||
- | {{: | + | {{: |
- | When configuring a router in a MultiWAN configuration, | + | When configuring a router in a MultiWAN configuration, |
- | Now, let's assume we have 2x WANs: | + | For example: |
- | WAN0=" | + | Let's assume we have 2 WANs, as follows: |
- | WAN1=" | + | WAN0=" |
- | At some point, WAN1 fails. As soon as the failure is noticed, WAN0 will bring itself to life and start to route packets. Later, WAN1 recovers its connectivity. As soon as FreshTomato recognizes this, (seconds to minutes), WAN0 is to go back idling while the traffic is re-routed by the resuscitated WAN1. This recovery, back to the originally active interface is also known as **preempting. Preempting is **the default (currently not configurable) behavior in FreshTomato.\\ | + | WAN1=" |
- | A very important | + | 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 405: | Line 405: | ||
* This is usually only for advanced users. \\ \\ | * This is usually only for advanced users. \\ \\ | ||
- | **Shared Key: | + | **Shared Key: |
- | **Group Key Renewal: | + | **Group Key Renewal: |
- | Starting with release 2023.5 | + | Starting with release 2023.5, you can adjust |
- | 1 sec up to 2592000 sec [for mips RT-N / mips-RT-AC | + | |
- | 0 => disabled (not recommended) | + | |
- | + | ||
- | Releases up to 2023.4 can adjust this value within the following limits: | + | |
- | 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] | ||