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 [2024/11/27 01:21] (current) – -Condense, formatting hogwild | ||
---|---|---|---|
Line 5: | Line 5: | ||
\\ | \\ | ||
- | **Boot Wait Time * :** | + | **Boot Wait Time * :** the time period during which you can access the router |
+ | |||
+ | This refers to the bootstrapping portion of the process, or the loading of code before the OS loads. If you need to delay the boot process (to stay in internal webserver CFE mode), change this setting. | ||
In rare circumstances, | In rare circumstances, | ||
- | {{: | + | \\ |
- | | + | {{: |
- | CTF lets bridges use an alternative forwarding method for storing | + | Only 10Mbps |
- | With CTF enabled, the router starts to send transmission frames as soon as the full packet header has been received. However, | + | (Default: Autonegotiate). |
+ | |||
+ | \\ {{: | ||
+ | |||
+ | CTF lets bridges use an alternative forwarding method for storing/ | ||
+ | |||
+ | With CTF enabled, the router starts to send transmission frames as soon as the full packet header has been received. However, | ||
+ | |||
+ | \\ | ||
**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. | **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. | ||
Line 30: | Line 40: | ||
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. | ||
Line 38: | Line 48: | ||
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 KBytes. If enabled, Jumbo Frame capability will be enabled on all LAN/WAN ports. | ||
- | This feature is only supported in 1000 Mb/s mode. Also, a gigabit | + | This feature is supported |
- | + | ||
- | Not all hardware 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 Kbytes. (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 | + | It is best to leave this disabled unless |
Not all hardware models support this feature. | Not all hardware models support this feature. |