This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| advanced-misc [2026/07/23 18:23] – -Condense, clarify and reformat CTF section hogwild | advanced-misc [2026/07/23 18:35] (current) – -Clarity, condense, formatting hogwild | ||
|---|---|---|---|
| Line 21: | 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 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: // | + | 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. |
| - | CTF can also cause issues with IPv6 tunneling protocols,** **like 6in4 Static. | + | \\ |
| + | |||
| + | 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 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. |
| + | |||
| + | Gigabit switches use more memory with this feature enabled. This can affect performance, | ||
| - | This feature is supported only in 1000 Mb/s mode. Also, gigabit switches use more memory with this feature enabled. This can affect performance, | + | 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 | + | Not all models support this feature. |
| ** **\\ | ** **\\ | ||
| Line 70: | Line 76: | ||
| **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 78: | 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 104: | 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: "/ |