Notes: 1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.10 and newer 2. krack fixes for Broadcom were completed in r33678, 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 Issue #4 below).
4.R6400v2 support added in r36811-36818, 36825, and 36826. R6700v3 support added in r36828-36840.
Issues, observations, and/or workarounds reported: 1. (egc) Policy-Based Routing broken if SFE enabled: 5900 quarkysg's PBR+SFE fix: 5986 2.Trendnet 81*DRU models are missing factory-to-flash 3.DNScrypt is mostly only using v2 protocols now, but requires Golang that DD can't use:6246 4.WDS does not work on ARM devices (only MIPS<->MIPS) 5.VAPs not working at boot (k3.10?); workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
6.K2.6 builds are broken since 38253(?); GUI issues:6538
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.
Last edited by flyzipper on Sun Feb 17, 2019 21:37; edited 1 time in total
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r38788 mini (02/15/19)
Kernel: Linux 4.4.174 #4690 Fri Feb 15 10:51:39 CET 2019 armv7l
Previous: r38581
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Update process went as usual and appears to be working, however the version reported is r38788 (not r38801).
Uptime: 21m
Temperatures: CPU 68.6 °C / WL0 50.5 °C / WL1 54.1 °C
Posted: Sun Feb 17, 2019 11:23 Post subject: wrong release number!
I have two different routers. One of them is Linksys wrt1900acsv2 and the other one is Linksys E3000. Both of them were r38581 before the firmware upgrade. After I successfully upgraded both of my router, I only see E3000 upgraded to r38801 and my other router, wrt1900acsv2 still shows r38581. I have not received any error messages during the upgrades. Then I repeated the upgrade process on my wrt1900acsv2 router again but the release number stayed the same, r38581.
Joined: 26 Mar 2013 Posts: 1856 Location: Hung Hom, Hong Kong
Posted: Mon Feb 18, 2019 4:17 Post subject: Automated directory comparison
kernel-panic69 wrote:
Yep, looks like this build was pulled off the server, thread topic should be changed to reflect...
I think a script should be written to compare the size of files in the HTTP/FTP directory of a new build against their counterparts in older builds. A file size difference over 20% (for example) should be reported. The script should also report missing directories.
I can do it in Visual Foxpro with ease. But then there are free, existing directory comparison tools for both Linux and Window$. _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
