SliderMike; I too prefer DD-WRT, that is why I'm so interested in this question and why I posted.
Hopefully BrainSlayer and other developers already knows the need for this and is working on it or will do so when Broadcom (and other chip manufacturers) release the necessary hardware information, meantime I'll (sadly) be on ASUS Merlin.
You could try loading one of kongs firmware (not the latest as it been disabled) for your router.
Kong had ddtb (ddwrt turbo I think it was called) enabled in a couple of the recent builds.
If you experience issues with it, just flash back to asus merlin.
Some users said it worked fine, others complained about this or that.
I never noticed a problem while I was running the firmware.
I don't have that sort of wan speed to tax non-ctf firmware. _________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
When I was running VDSL2 recently everything was fine, as soon as the fiber was installed I got problems (the WNDR3700 I got couldn't communicate with the fiber modem and the RT-N66U & RT-AC66U lost most of the fiber speed/performance).
But right now, when using Merlin on the RT-AC66U the communication with the modem works and no speed is lost (actually not a single Megabit (which is impressive in itself I think)).
So again, developers of DD-WRT; hope that you can solve the problem with hardware NAT acceleration / ctf soon so me and others in the same situation can go back to our beloved DD-WRT!
Posted: Fri Nov 27, 2015 17:56 Post subject: Command to re-enable it if one wants to try...
I'm using dd-wrt.v24-28366_NEWD-2_K3.x_mega-WNDR4500 and I was wondering how one could re-enable the Hardware NAT if one wants to give it a try. Googled around for it, but don't see anyone explaining how to turn it on..
Posted: Fri Nov 27, 2015 21:29 Post subject: Re: Command to re-enable it if one wants to try...
I was wondering how one could re-enable the Hardware NAT if one wants to give it a try.
You can't...it was only an experimental addition (by Kong I think, briefly) a year or two ago. You have to use OEM s/w for hardware NAT. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: Builds, Types, Modes, Changelog, Peacock, Demo#
x64 OPNsense 19.1.1|EA6900v1.1@1GHz FT 2019.1beta|DD 38744: WNDR4500v2, WNDR4000@533, E1500@353, R6300v1,
2*E2500, WRT54*@250: GLv1.1 nsg, GSv6 µ|RT-N66U@663 Merlin 380.70|OEM: WGR614v10@400-WNR1000v3 mod
Joined: 06 Jun 2006 Posts: 6806 Location: Dresden, Germany
Posted: Sat Nov 28, 2015 0:51 Post subject:
ctf is impossible since its incompatible with any kernel different from broadcoms. the ctf driver is also only provided as binary. (even if i have a nda with broadcom and own all sourcecodes for wireless drivers. no vendor in this world got ever the ctf sourcecode)
but this is no hw nat acceleration. ctf is a software hotpath to accelerate bridged networks. but not nat.
hw nat acceleration might bring some benefits, but some really poor problems.
hw nat acceleration does not take care about any special firewall settings.
it all. it will break alot of iptables specific rules.
current cpu's are fast enough anyway to handle any sort of traffic.
some devices like newer broadcom devices do also offer complete wireless offloading, since chipsets own a own cpu with a own micro os. so the main cpu isnt that busy with handling the wireless stack etc.
so the answer is. some devices/architectures do support hw offloading features which are supported.
but broadcom ctf is no hw acceleratin or hw offloading. its a kernel hack to override the network stack and bypass the complete network stack to make it faster. but bypassing means it bypasses really everything, also features you will miss at the end.
we played with a own ctf like driver one year ago, but it was never finished and had the same troubles with filtering like described here _________________ one cigarette costs 2 minutes of your life.
one bottle of beer costs 4 minutes of your life.
one working day costs 8 hours of your life.
Linux DD-WRT 4.14.8 #42 SMP PREEMPT Thu Dec 21 18:11:16 CET 2017 armv7l DD-WRT
root@DD-WRT:/sys# nvram get DD_BOARD