This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| advanced-misc [2024/11/01 20:39] – -Condense hogwild | advanced-misc [2026/03/12 01:42] (current) – hogwild | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| \\ | \\ | ||
| - | **Boot Wait Time * :** the time period during which you can access the router via its CFE webserver. This refers to the bootstrapping portion of the process, or the loading of code before the operating system | + | **Boot Wait Time** *: the period during which you can access the router via its CFE webserver. |
| + | |||
| + | This refers to the bootstrapping portion of the process, or the loading of code before the OS loads. | ||
| In rare circumstances, | In rare circumstances, | ||
| Line 11: | Line 13: | ||
| \\ | \\ | ||
| - | {{: | + | {{: |
| + | |||
| + | Only 10Mbps and 100Mbps speeds can be forced. For 1Gpbs, leave it at Autonegotiate. Not all models support this feature. | ||
| + | |||
| + | (Default: Autonegotiate). | ||
| \\ {{: | \\ {{: | ||
| - | CTF lets bridges use an alternative forwarding method for storing | + | CTF lets bridges use an alternative forwarding method for storing/forwarding frames. Enabling |
| - | With CTF enabled, the router starts to send transmission frames as soon as the full packet header has been received. However, | + | With CTF enabled, the router starts to send transmission frames as soon as the full packet header has been received. However, |
| \\ | \\ | ||
| - | **Enabling CTF disables QoS and Bandwidth Limiter**. | + | **Enabling CTF disables QoS / Bandwidth Limiter**. It can also cause issues for IPv6 tunneling protocols,** **like 6in4 Static. |
| - | With CTF disabled, the router stores the entire frame before sending it out to its destination. | + | This is because the switching part of the packet bypasses parts of the standard Linux iptables chains. |
| + | |||
| + | With CTF disabled, the router stores the entire frame before sending it to its destination. | ||
| When this happens: | When this happens: | ||
| Line 31: | Line 39: | ||
| \\ | \\ | ||
| + | |||
| + | FastNAT is a similar function that forwards frames at accelerated speeds. | ||
| CTF/FastNAT is supported as follows: | CTF/FastNAT is supported as follows: | ||
| Line 37: | Line 47: | ||
| * MIPS RT-N routers (like the E4200v1, RT-N16) can use Broadcom FastNAT | * MIPS RT-N routers (like the E4200v1, RT-N16) can use Broadcom FastNAT | ||
| * MIPS RT-AC routers (like the RT-AC66U) do not support CTF or FastNAT. | * MIPS RT-AC routers (like the RT-AC66U) do not support CTF or FastNAT. | ||
| - | |||
| - | \\ FastNAT is a similar function that forwards frames at accelerated speeds. | ||
| On ARM devices, you can expect performance in the range of 200 to 400 Mb/s with CTF enabled. | On ARM devices, you can expect performance in the range of 200 to 400 Mb/s with CTF enabled. | ||
| - | \\ **Enable Jumbo Frames: | + | \\ |
| + | |||
| + | **Enable Jumbo Frames: | ||
| The default Jumbo Frames size is 2 KBytes. If enabled, Jumbo Frame capability will be enabled on all LAN/WAN ports. | The default Jumbo Frames size is 2 KBytes. If enabled, Jumbo Frame capability will be enabled on all LAN/WAN ports. | ||
| - | This feature is supported only in 1000 Mb/s mode. Also, gigabit switches use more memory | + | This feature is supported only in 1000 Mb/s mode. Also, gigabit switches use more memory |
| + | |||
| + | \\ | ||
| + | |||
| + | **Jumbo Frame Size:** if enabled, overrides default frame size. | ||
| + | |||
| + | If disabled, default frame size is 2 KB. (Default: off). Generally, enable Jumbo Frames if you frequently transfer large files within your LAN. To function, all devices must support Jumbo Frames. You should also standardize the packet size across all LAN devices. | ||
| + | |||
| + | It's best to leave this disabled unless you have specific requirements for it. Using Jumbo Frames means Internet traffic will be fragmented, unless the end device supports Path MTU Discovery. Often, the limited performance benefits of Jumbo Frames isn't worth the time and effort needed to tune/ | ||
| Not all hardware models support this feature. | Not all hardware models support this feature. | ||
| + | |||
| + | ** **\\ | ||
| + | |||
| + | **Port Health:** Since r2025.5, this watchdog counts errors on Ethernet connections and takes a defined action when an exception is spotted. | ||
| + | |||
| + | This function was introduced to prevent a bad Ethernet cable to take your router down (eating up CPU cycles) and making the device unresponsive. | ||
| + | |||
| + | \\ \\ {{port_health.png? | ||
| + | |||
| + | | ||
| + | |||
| + | **Enable:** runs the porthealth process to monitor the defined ports scope, every minute. | ||
| + | |||
| + | The check is extremely lightweight and executes in about 0.02 - 0.04 seconds. | ||
| \\ | \\ | ||
| - | **Jumbo Frame Size:** If enabled, its setting overrides default frame size. When disabled, default frame size is 2 Kbytes. | + | **Mode: **determines the script’s level of intervention when it detects network errors |
| - | Generally, enable Jumbo Frames if you frequently transfer large files within | + | Essentially, this sets the " |
| - | It is best to leave this disabled unless you have specific requirements for it. Using Jumbo Frames means Internet traffic will be fragmented, unless the end device supports Path MTU Discovery. Often, the limited performance benefits of Jumbo Frames isn't worth the time and effort needed to tune/ | + | \\ |
| - | Not all hardware | + | * Monitor (log only) - the passive mode. This acts as an early warning system without \\ changing |
| \\ | \\ | ||
| + | |||
| + | * Recover - the active/ | ||
| \\ | \\ | ||
| + | |||
| + | * Disable port - the **aggressive** mode. It follows a " | ||
| \\ | \\ | ||
| + | |||
| + | **Ports: **defines the type of logical ports to be monitored. For example, LAN only, WAN only or LAN + WAN. | ||
| + | |||
| + | \\ | ||
| + | |||
| + | **Max Errors / Minute **AKA: " | ||
| + | |||
| + | Under most circumstances, | ||
| + | |||
| + | \\ | ||
| + | |||
| + | **Hold Time: **acts as " | ||
| + | |||
| + | In this context, it is ideal for the router to have a " | ||
| + | |||
| + | \\ | ||
| + | |||
| + | **Cache TTL** - defines how often the script performs the "heavy lifting" | ||
| + | |||
| + | Identifying which ports are active involves more than just scanning them individually for errors. The script saves the list of active ports to a file in: "/ | ||