This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
advanced-misc [2023/09/25 17:40] – -add further depth to CTF section hogwild | advanced-misc [2023/09/25 21:40] – hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Miscellaneous ====== | ====== Miscellaneous ====== | ||
- | This page allows | + | In this menu, you can tweak some secondary, less critical |
+ | |||
+ | \\ | ||
**Boot Wait Time * :** This is the time period during which a router can be accessed using the included CFE webserver. This refers to the bootstrap portion of the process, or the loading of code before the Operating system loads. If you need to delay the s boot process (to stay in internal webserver CFE mode), change this setting. In rare circumstances, | **Boot Wait Time * :** This is the time period during which a router can be accessed using the included CFE webserver. This refers to the bootstrap portion of the process, or the loading of code before the Operating system loads. If you need to delay the s boot process (to stay in internal webserver CFE mode), change this setting. In rare circumstances, | ||
Line 9: | Line 11: | ||
\\ {{: | \\ {{: | ||
- | CTF uses an alternative forwarding method | + | CTF lets bridges use an alternative forwarding method |
- | With CTF enabled, the router starts to send out transmission frames as soon as it receives its destination. 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. Note that enabling CTF will disable QoS and Bandwidth Limiter. This is because the switching part of the packet bypasses parts of the standard Linux iptable chains. | + | With CTF enabled, the router starts to send out 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. Note that enabling CTF will disable QoS and Bandwidth Limiter. This is because the switching part of the packet bypasses parts of the standard Linux iptable chains. |
- | When you have CTF disabled, the router will store the entire frame before sending it out to its destination. When this happens: | + | With CTF disabled, the router will store the entire frame before sending it out to its destination. 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 |
- | * For example, CTF could allow you to use your FreshTomato device in a Gigabit WAN environment. On ARM devices, you can expect performance in the range of 200 to 400 Mb/s. | + | |
- | \\ | + | CTF/FastNAT is supported as follows: |
* ARM Routers (like the RT-AC68U, RT-AC3200, R7000) 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 | ||
* FastNAT is a similar function to forward at accelerated speeds. | * FastNAT is a similar function to forward at accelerated speeds. | ||
Line 28: | Line 30: | ||
\\ | \\ | ||
- | **Enable Jumbo Frames * :** This option allows you to increase the maximum frame size within the LAN. (Default: | + | On ARM-based devices, you can expect performance in the range of 200 to 400 Mb/s with CTF enabled. |
+ | |||
+ | | ||
The default size for Jumbo Frames is 2000 bytes. If enabled, all ports (WAN + LAN) will have Jumbo Frame capability enabled. | The default size for Jumbo Frames is 2000 bytes. If enabled, all ports (WAN + LAN) will have Jumbo Frame capability enabled. |