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/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 * :** 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 loads. If you need to delay the boot process (to stay in internal webserver CFE mode), change this setting. | + | **Boot Wait Time** *: the period during which you can access the router via its CFE webserver. |
| - | 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 if you need to delay the boot process (to stay in internal webserver CFE mode). |
| + | |||
| + | Rarely, such as in a power outage, your modem might take longer to boot than FreshTomato does. This setting | ||
| \\ | \\ | ||
| - | {{: | + | {{: |
| + | |||
| + | 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 | + | With CTF enabled, the router |
| \\ | \\ | ||
| - | **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. | + | For example: //**Enabling CTF disables QoS / Bandwidth Limiter**//. |
| - | With CTF disabled, the router stores the entire frame before sending it out to its destination. | + | 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: | ||
| Line 38: | Line 48: | ||
| * 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. | ||
| - | \\ **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 KB. If enabled, Jumbo Frame capability will be enabled on all LAN/WAN ports. This feature is supported only in 1000 Mb/s mode. |
| - | This feature is supported only in 1000 Mb/s mode. Also, gigabit | + | Gigabit |
| - | Not all hardware | + | 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. |
| - | 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/ | + | Leave this disabled unless you have specific requirements for it. Unless the end device supports Path MTU Discovery, using Jumbo Frames means Internet traffic will be fragmented. Often, the limited performance benefits of Jumbo Frames isn't worth the time and effort needed to tune/ |
| - | 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: "/ | ||