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/20 19:13] – [WAN(x) Settings] -clarity, condense of WAN load weight hogwild | basic-network [2024/02/21 02:27] – [WAN(x) Settings] -clarity-load balance weight limitations 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 2x WANs with: |
- | WAN1=" | + | WAN0=" |
- | At some point, WAN1 fails. As soon as the failure is noticed, WAN0 will bring itself to life and begin routing packets. Later, WAN1 recovers its connectivity. As soon as FreshTomato recognizes this, (seconds to minutes), WAN0 will go back to an idle status while the traffic is re-routed through the resuscitated WAN1. This recovery, back to the originally active interface is also known as **preempting. **Preempting is FreshTomato' | + | WAN1=" |
- | 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 // |
\\ | \\ |