CTF is pure software acceleration, FA is Hardware acceleration so when both are enabled not only are you using both CPU's( for CTF) you are also using specific in chip hardware accelerator, but FA is really for Gigabit WAN speeds anything less CTF should be fine.
the-joker you are totally correct. I read on another thread which you just posted that to use FA you need to reboot twice. I did that, and it made a big difference when I connected it to my test Comcast high speed internet connection. I get substantially higher speeds than just CFT alone. (Both wired and Wi-Fi).
wait. Did some new option show up after rebooting twice? What exactly does the 2nd reboot do?
Joined: 01 Dec 2021 Posts: 289 Location: Maryland, United States
Posted: Sat Jun 25, 2022 13:06 Post subject:
When you select FA and apply it a reboot will happen but it appears even though it is shown to be implemented it is not, a second reboot is needed to activate it.
Last edited by PaulGo on Sat Jun 25, 2022 15:25; edited 1 time in total
Correction: Using CFT+FA for Flow Acceleration is faster. To implement this I needed to reboot my router twice.
Does this work with QoS on too?
To solidify previous answer, you cannot use any Shortcut Forwarding Engine mode configuration with QoS in DD-WRT;
you have *never* been able to do this.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Sat Jun 25, 2022 16:57 Post subject:
IDK what you guys are smoking, but its rude not to share. The Joker has jokes
Ive already explained on some thread in some detail the limitations and caveats of using CTF and CTF & FA, but it seems its been missed entirely.
caveats wrote:
NAT Acceleration supports only adaptive QoS (Level 1 CTF), no QoS (Level 2 CTF+FA), may not support port forwarding (hosting game servers, etc.), parental controls, PPPoE, STP. The increased re-transmission caused by NAT Acceleration may also cause shuttering on some streaming devices (Apple TV, Chromecast, VoIP).
And again for the crowd on the back seats, because of how FA works using on chip acceleration, one reboot to bring this online, second to get the right modules loaded, or the other way around, this is closed source crap so there no way to look at what the code does.
When you select FA and apply it a reboot will happen but it appears even though it is shown to be implemented it is not, a second reboot is needed to activate it.
how are you testing (and what results are you seeing) between it working and not working?
the-joker wrote:
IDK what you guys are smoking, but its rude not to share. The Joker has jokes
Ive already explained on some thread in some detail the limitations and caveats of using CTF and CTF & FA, but it seems its been missed entirely.
caveats wrote:
NAT Acceleration supports only adaptive QoS (Level 1 CTF), no QoS (Level 2 CTF+FA), may not support port forwarding (hosting game servers, etc.), parental controls, PPPoE, STP. The increased re-transmission caused by NAT Acceleration may also cause shuttering on some streaming devices (Apple TV, Chromecast, VoIP).
And again for the crowd on the back seats, because of how FA works using on chip acceleration, one reboot to bring this online, second to get the right modules loaded, or the other way around, this is closed source crap so there no way to look at what the code does.
Not very long ago the CTF/CTF&FA detection code was re-written, so only specific platforms that support it will show the CTF&FA option, now its possible some #ifdef is in wrong place for some routers, but tbh I dont give this too much attention, this code is part of DD-WRT so its out there for auditing.
Is there a way to check if its fully loaded and operational? Maybe NVRAM value? or Process running?
Router: Asus RT-AC66U.
Mode: AP.
File: dd-wrt-48322-Asus_RT-AC66U.trx
Kernel: well, the one included in the build.
Reset: no.
Status: WORKING. All seems fine.
Previous build: dd-wrt-48540-Asus_RT-AC66U (05/04/22).
Uptime: one day.
Flashed via: GUI. _________________ My router: Asus RT-AC66U
Operating systems on devices that I use with that router: GNU-Linux; Windows 10; Android 13