Differences

This shows you the differences between two versions of the page.

--- basic-network [2023/09/12 17:40] – [Wireless (5 GHz / interface eth2)] hogwild
+++ basic-network [2024/02/21 17:54] (current) – [WAN(x) Settings] -clarify Load Balance Weight and add OOO explanation hogwild
@@ Line 92: / Line 92: @@
  \\
+ \\
+**Load Balance Weight:   **This option is** **visible only when number of WANs > 1. It can be set between 0 and 256.\\
+{{:pasted:20240219-103900.png}}\\  \\
+When configuring a router in a MultiWAN configuration, the MultiWAN function performs load sharing of the links. Load sharing is performed on a per-session basis to prevent issues with interactive traffic, such as real-time voice/video, or RDP. The reason for this is that your links might have different speeds and per-packet load-sharing would generate OOO (Out-of-order) packets, which could make interactive traffic pretty much unusable. Setting a Load Balance Weight on each interface adjusts how that interface will participate in MultiWAN activities. Below are some examples.\\  \\ Load Balance Weight: 0  (Failover)\\ If 0 is used, FreshTomato will not actively route traffic if other WAN interfaces are functional. However, the WAN connection with weight "0" will be automatically enabled if there is a failure of all other WAN interfaces with a weight or 1 or more. This is commonly used in "failover" scenarios. When an interface with weight "0" is is automatically enabled, it will be assigned a weight of 1.
+For example:
+Let's assume we have 2 WANs, as follows:
+WAN0="weight 0"
+WAN1="weight 1"
+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 //preempting//.** **FreshTomato uses Preempting as its default (and fixed) behavior.\\  \\ Load Balance Weight: 1\\ Any value higher than "0" causes an interface to actively route packets. Weights are relative, so a weight of "1" doesn't mean much. Each weight is compared to the Load Balance Weights of other Interfaces to direct functionality. One way of understanding this is to remember: "1=100% and 0=0%". Thus, if WAN0=“weight 0” and WAN1=“weight 1”, that would mean WAN1 is handling 100% of the traffic.\\  \\ Load Balance Weight: 5\\ An interface set with, for example, weight 5, would essentially handle 5 new sessions before any other interface is to be used.\\  \\ For example, say we have 3 WANs, as follows:\\  \\  WAN0 = weight 0\\  WAN1 = weight 1\\  WAN2 = weight 5\\  \\ In this case, WAN0 will be used only if both WAN1 and WAN2 are both in a failed state, and are unable to route packets. WAN1 will handle the very first new LAN client session going through the router. WAN2 is set to handle the second, third, fourth, fifth and sixth sessions. The seventh new session starts again from WAN1, as it would be treated as a another first new LAN client session. WAN2 will then handle the next five new sessions, meaning the eighth, ninth, tenth eleventh and twelfth sessions.\\   \\ One final point about MultiWAN load sharing: **These settings only affect outbound traffic**. Return traffic will always try to return to the WAN interface from which it originated. As the allocation of new session to a WAN is dynamic, you could control what traffic gets allocated to which Interface (a.k.a. sticky connection) via the [[advanced-pbr|MultiWAN routing]] configuration page.
  \\
@@ Line 387: / Line 405: @@
     * This is usually only for advanced users. \\ \\
-**Shared Key:**  Here, enter the shared key to authenticate WiFi clients on the LAN. The field shows asterisks until you click your cursor in it. \\ \\
+**Shared Key:**  Here, enter the shared key to authenticate WiFi clients on the LAN. Asterisks are shown until you insert your cursor. \\ \\
+**Group Key Renewal:**  This sets how often encryption keys used between clients and the router are rotated/changed. \\ This is a part of the WPA protocol. (Default: 3600 seconds = 1 hour).
+Starting with release 2023.5, you can adjust the key rotation interval within the following limits:\\ From 1 sec to 2592000 sec   [for all ARM routers and MIPS RT-N / MIPS-RT-AC] \\ 0 = disabled   (not recommended)
-**Group Key Renewal:**  This sets how often encryption keys are used between clients and the router/AP are rotated/changed. \\ This is a part of the WPA protocol. (Default: 3600 seconds = 1 hour).
+In releases up to 2023.4, you can set this within the following limits: 60 sec to 7200 sec [all routers]
@@ Line 502: / Line 524: @@
 **Group Key Renewal:**  This sets how often encryption keys used between clients and the router are rotated. This is part of the WPA protocol.
-(Default: 3600 seconds).
+(Default: 3600 seconds). Please see the first wireless radio unit for more infos!

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools