This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| advanced-misc [2026/07/18 17:57] – pedro | 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. |
| \\ | \\ | ||
| Line 9: | Line 9: | ||
| 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). | 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). | ||
| - | In rare circumstances, such as a power outage, your modem might take longer to boot than FreshTomato does. This setting | + | Rarely, such as in a power outage, your modem might take longer to boot than FreshTomato does. This setting |
| - | {{:clipboard01.jpg?400}} \\ | + | \\ |
| + | |||
| + | {{:pasted: | ||
| Only 10Mbps and 100Mbps speeds can be forced. For 1Gpbs, leave it at Autonegotiate. Not all models support this feature. | Only 10Mbps and 100Mbps speeds can be forced. For 1Gpbs, leave it at Autonegotiate. Not all models support this feature. | ||
| Line 19: | Line 21: | ||
| \\ {{: | \\ {{: | ||
| - | CTF lets bridges use an alternative forwarding method for storing/ | + | CTF lets bridges use an alternative forwarding method for storing/ |
| - | With CTF enabled, the router | + | With CTF enabled, the router |
| \\ | \\ | ||
| - | **Enabling CTF disables QoS / Bandwidth Limiter**. It can also cause issues for IPv6 tunneling protocols, | + | For example: //**Enabling CTF disables QoS / Bandwidth Limiter**//. |
| - | This is because the switching part of the packet bypasses parts of the standard Linux iptables chains. | + | CTF can also cause issues with IPv6 tunneling protocols, |
| With CTF disabled, the router stores the entire frame before sending it to its destination. | With CTF disabled, the router stores the entire frame before sending it to its destination. | ||
| Line 34: | Line 36: | ||
| * 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 |
| \\ | \\ | ||
| Line 45: | 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. | ||
| + | |||
| + | \\ | ||
| 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. | ||
| Line 52: | Line 56: | ||
| **Enable Jumbo Frames:** lets you increase the maximum frame size on the LAN. (Default: disabled). | **Enable Jumbo Frames:** lets you increase the maximum frame size on the LAN. (Default: disabled). | ||
| - | 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 models support this feature. | ||
| \\ | \\ | ||
| Line 62: | Line 68: | ||
| 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. | 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/ | + | 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 models support this feature. | + | |
| - | + | ||
| - | ** ** | + | |
| - | + | ||
| - | **TCP MSS Clamping: | + | |
| - | + | ||
| - | TCP MSS Clamping adjusts the Maximum Segment Size of forwarded TCP connections on WAN and VPN interfaces to match the discovered path MTU. | + | |
| - | + | ||
| - | This helps avoid MTU-related connection problems, especially on PPPoE links, VPN tunnels, IPv6 tunnels, or networks where ICMP fragmentation-needed messages are blocked. | + | |
| - | Disabling | + | Not all models support |
| - | Recommended setting: enabled, unless MTU/MSS is handled manually or the network is known to work reliably without MSS clamping.\\ | + | ** **\\ |
| **Port Health:** Since r2025.5, this watchdog counts errors on Ethernet connections and takes a defined action when an exception is spotted. | **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 | + | This function was introduced to prevent a bad Ethernet cable to take your router down (eating up CPU cycles) and making |
| \\ \\ {{port_health.png? | \\ \\ {{port_health.png? | ||
| Line 88: | Line 84: | ||
| **Enable:** runs the porthealth process to monitor the defined ports scope, every minute. | **Enable:** runs the porthealth process to monitor the defined ports scope, every minute. | ||
| - | The check is extremely | + | The check is lightweight and executes in about 0.02 - 0.04 seconds. |
| \\ | \\ | ||
| Line 114: | Line 110: | ||
| \\ | \\ | ||
| - | **Max Errors / Minute **AKA: " | + | **Max Errors / Minute **AKA: " |
| - | Under most circumstances, you'd expect the number of errors to be " | + | Usually, you'd expect the number of errors to be " |
| \\ | \\ | ||
| - | **Hold Time: **acts as " | + | **Hold Time: **acts as " |
| - | In this context, | + | In this context, the router |
| \\ | \\ | ||
| - | **Cache TTL** - defines | + | **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: "/ | + | 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: "/ |