Notes: 1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.2 and newer 2. 'KRACK' vulnerability fixes were completed in r33678 for Broadcom, including k26 (33655) & k24 (33656); use build 33772 or later.
3. Bridge modes on k4.4 devices may sometimes work in some configurations in certain builds but are not supported by the bcmdhd driver. Use client or repeater instead as WDS doesn't work with Broadcom ARM either (see Issues below).
4. Since 39469, udhcpd was removed and replaced with the already present dnsmasq, and PIE qdisc was added for some builds.
5. Policy-Based Routing with SFE enabled was fixed in r39556: 5986 and 5900 6. k2.4 (broadcom/) builds were fixed in 39715 (broken in 39144 through 39654)
7.SFE update (k3.10+ for BCM) was in the 39927 build.
Issues, observations, and/or workarounds reported: 1.Trendnet 81*DRU models are missing factory-to-flash 2.DNScrypt is mostly only using v2 protocols now, but requires Golang that DD can't use:6246 3.WDS does not work on Broadcom ARM devices (only MIPS<->MIPS) 4.K2.6 builds are broken since 38253(?) (GUI issues):6538 5.VAPs not working at boot; workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
This appears to be fixed for some routers (different kernels, modes, and radios) since build 39508. 6.UDP forwarding might not work with SFE Enabled: 6668
Important: if any issues are found, please provide log info (GUI syslog, `dmesg`, `cat /var/log/messages`).
Or put into SVN ticket. For firewall issues, also provide "iptables" info (`iptables -L`, `iptables -t nat -L`, & the /tmp/.ipt file).
Template to copy (after "Code:") for posting issues, be sure to include the mode in use (gateway, AP, CB, etc.):
WARNING:This thread is to report on flashing this experimental test build, providing important info for both developers and users. Always state your hardware model, version, mode (e.g. Repeater) and SPECIFIC build (e.g. 33555_NEWD-2_K3.x_mega-nv64k.bin). Please avoid discussions and create a new thread to discuss specific problems or questions, as this thread is for reporting, not support. Posts may be deleted or moved to keep this thread manageable and useful. If you don't understand the risks or what to flash and how, with a means of recovery if it bricks, do NOT flash this experimental test build.
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r40501 std (08/02/19)
Kernel: Linux 4.4.186 #584 SMP PREEMPT Fri Aug 2 11:18:37 +04 2019 armv7l
Previous: r40459
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Working so far (SFE remains disabled because its UDP forwarding issues continue to periodically mess with my Xbox Live gaming experience).
Edit... this build (or my ISP) hasn't been very stable for the last 24hrs. Will try a reset/re-config if it persists.
Uptime: 24min
Temperatures: CPU 69.7 °C / WL0 48.6 °C / WL1 54.6 °C
Last edited by flyzipper on Sun Aug 04, 2019 9:27; edited 1 time in total
Router/Version: Linksys EA6300
Firmware: DD-WRT v3.0-r40501 std (08/02/19)
Kernel: Linux 4.4.186 #584 SMP PREEMPT Fri Aug 2 11:18:37 +04 2019 armv7l
Previous: 07-29-2019-r40452
Mode/Status: Gateway/VAP/WireGuard
Reset: Must, without Reset, system is very unstable
Issues/Errors: workaround is needed for VAP
ERROR when I try to write linux2 MTD device
root@ddwrt:/tmp# mtd -f write linksys-ea6400-webflash.bin linux2
Unlocking linux2 ...
Could not unlock MTD device: linux2
linux2: Not supported
Writing from linksys-ea6400-webflash.bin to linux2 ... [e]Failed to get erase block status
I don't know, the operate to write to linux2 is successful ?
errors
Dec 31 19:00:12 DD-WRT kern.warn kernel: CONSOLE: 000000.000 initvars_srom_pci, SROM CRC Error
Dec 31 19:00:12 DD-WRT kern.warn kernel: CONSOLE: 026738.601 initvars_srom_pci, SROM CRC Error
Dec 31 19:00:12 DD-WRT kern.warn kernel: CONSOLE: 026738.633 initvars_srom_pci, SROM CRC Error
Dec 31 19:00:12 DD-WRT kern.warn kernel: CONSOLE: 026738.666 initvars_srom_pci, SROM CRC Error
Dec 31 19:00:13 DD-WRT daemon.info mstpd[621]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 10
Dec 31 19:00:13 DD-WRT daemon.info mstpd[621]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 10
your device has no real jffs, but ubifs volume which is normally used for plex... this big flash space can be used by dd-wrt but only if BS do some of his tricks... try next public...
thanks for the explanation. the space was used for bloatware in the factory firmware. it had a disney parental controls. an antivirus. some usb sharing etc.
i was pointing it out because it just recently went missing. it has been in there working fine in previous builds. is it normal for things to come and go?
Last edited by tinkeruntilitworks on Wed Aug 07, 2019 20:56; edited 2 times in total
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Sat Aug 03, 2019 16:43 Post subject:
To quote a line from a movie, "...at the whim of a madman..." ... I didn't see any specific commits that would've removed /jffs2 functionality from any specific device, but I can back-track.
another thing
are those errors worth posting. i just go through to log searching the word error. the bridge one I know is known and i believe is across the board. the other im unsure.
Issues/Errors: Web-GUI become unresponsive after 30 minutes of use.
However, the router remain functional for a good 1 hour and 30+ mins, before the connections become really slow and eventually unresponsive.
A reset on the Router allows it to come back to life, along with my further observation. The CPU load is gradually rising to 100% till the Web-GUI become unresponsive again.
Another note, since I always do a reset to factory default and configure. The SFE was disabled by default. I'm not sure if this is related or not.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Sun Aug 04, 2019 17:24 Post subject:
I'm trying to figure out why some devices are locking up so badly, because my old dinosaur E4200 seems to not have these issues since I quit leaving ttraf daemon enabled and disabled uPnP.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Sun Aug 04, 2019 18:21 Post subject:
tinkeruntilitworks wrote:
leaving the traffic counter on causes issues?
I don't think it's ever been completely 'fixed', everything I've ever read said it was a broken piece of junk and caused issues. I don't need it's functionality, anyway.