This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| advanced-misc [2024/10/07 02:16] – -Resize screenshot "pasted:20220428-100039.png" to 443x257 hogwild | advanced-misc [2026/07/23 18:35] (current) – -Clarity, condense, formatting hogwild | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Miscellaneous ====== | ====== Miscellaneous ====== | ||
| - | In this menu, you can tweak some secondary, less critical | + | In this menu, you can tweak some more minor settings. These rarely need to be modified. If you change them, make sure you understand the consequences of those changes. |
| \\ | \\ | ||
| - | **Boot Wait Time * :** | + | **Boot Wait Time** *: the period during which you can access the router |
| - | In rare circumstances, such as a power outage, your modem might take longer to boot than FreshTomato does. This setting | + | This refers to the bootstrapping portion of the process, or the loading of code before the OS loads. Change this setting |
| - | {{: | + | Rarely, such as in a power outage, your modem might take longer |
| - | | + | \\ |
| - | CTF lets bridges | + | {{: |
| - | With CTF enabled, the router starts to send transmission frames as soon as the full packet header has been received. However, the router relies on the client device to tell it whether the data is corrupted for resend. This restriction can cause problems with a few common home uses. | + | Only 10Mbps and 100Mbps speeds can be forced. For 1Gpbs, leave it at Autonegotiate. Not all models support this feature. |
| - | **Enabling CTF disables QoS and Bandwidth Limiter**. **It can also cause issues for IPv6 tunneling protocols, **like 6in4 Static. This is because the switching part of the packet bypasses parts of the standard Linux iptable chains. | + | (Default: Autonegotiate). |
| - | With CTF disabled, the router stores the entire frame before sending it out to its destination. | + | \\ {{: |
| + | |||
| + | CTF lets bridges use an alternative forwarding method for storing/ | ||
| + | |||
| + | With CTF enabled, the router sends transmission frames as soon as it receives the full packet header. However, it relies on the client to tell it whether the data is corrupted for resend. This restriction can cause problems with a few common home uses. | ||
| + | |||
| + | \\ | ||
| + | |||
| + | For example: // | ||
| + | |||
| + | CTF can also cause issues with IPv6 tunneling protocols, | ||
| + | |||
| + | With CTF disabled, the router stores the entire frame before sending it to its destination. | ||
| When this happens: | When this happens: | ||
| * The holding period may require more of the router' | * The holding period may require more of the router' | ||
| - | * WAN-to-LAN performance | + | * WAN-to-LAN performance |
| \\ | \\ | ||
| + | |||
| + | FastNAT is a similar function that forwards frames at accelerated speeds. | ||
| CTF/FastNAT is supported as follows: | CTF/FastNAT is supported as follows: | ||
| - | * ARM Routers (RT-AC68U, RT-AC3200, R7000, etcetera) support CTF. | + | * ARM Routers (like the RT-AC68U, RT-AC3200, R7000) support CTF. |
| * 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. | ||
| - | | + | \\ |
| 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. | ||
| - | | + | \\ |
| - | The default | + | **Enable |
| - | This feature is only supported | + | The default Jumbo Frames size is 2 KB. If enabled, Jumbo Frame capability will be enabled on all LAN/WAN ports. |
| - | Not all hardware | + | Gigabit switches use more memory with this feature enabled. This can affect performance, |
| + | |||
| + | Not all models support this feature. | ||
| \\ | \\ | ||
| - | **Jumbo Frame Size: | + | **Jumbo Frame Size: |
| - | 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. | + | 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. |
| - | You are strongly advised to leave this disabled unless | + | Leave this disabled unless |
| - | Not all hardware | + | Not all 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 it unresponsive. | ||
| + | |||
| + | \\ \\ {{port_health.png? | ||
| + | |||
| + | | ||
| + | |||
| + | **Enable:** runs the porthealth process to monitor the defined ports scope, every minute. | ||
| + | |||
| + | The check is lightweight and executes in about 0.02 - 0.04 seconds. | ||
| \\ | \\ | ||
| + | |||
| + | **Mode: **determines the script’s level of intervention when it detects network errors (a " | ||
| + | |||
| + | Essentially, | ||
| \\ | \\ | ||
| + | |||
| + | * Monitor (log only) - the passive mode. This acts as an early warning system without \\ changing hardware settings. It compares the current error count against the baseline. \\ If the delta exceeds your threshold, it writes a warning to the system log (logger). \\ Use this to gather data or troubleshoot a " | ||
| \\ | \\ | ||
| + | |||
| + | * 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: " | ||
| + | |||
| + | Usually, you'd expect the number of errors to be " | ||
| + | |||
| + | \\ | ||
| + | |||
| + | **Hold Time: **acts as " | ||
| + | |||
| + | In this context, the router should ideally have a " | ||
| + | |||
| + | \\ | ||
| + | |||
| + | **Cache TTL** - 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: "/ | ||