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.
Last edited by kernel-panic69 on Fri Jul 26, 2019 23:02; edited 2 times in total
as I have posted in the r40400 post. It didn't flash on the RT-AC3200. Had to use CFE recovery _________________ ASUS RT-AC3200 - Deployed Client's site
ASUS RT-AC5200 - Merlin
ASUS RT-AX88U - Merlin
I am in the process of checking commits between 40400 and 40439 to see what the possible culprit is, well, I am trying, but svn is choking on it's own vomit.
damn. i was too eager.
bricked my r7000p
no clue how to save
if it's salvageable
can't get anything to connect to it
can't get it to reset
can't get it to boot up
lights flash like it's about to
then straight to amber power light
damn. i was too eager.
bricked my r7000p
no clue how to save
if it's salvageable
can't get anything to connect to it
can't get it to reset
can't get it to boot up
lights flash like it's about to
then straight to amber power light
Check the commits, someone with the same Router as you has also bricked his router, maybe he has a way to recover it, it wasnt that bad, i just used the factory recover procedure and everything fixed in seconds!
damn. i was too eager.
bricked my r7000p
no clue how to save
if it's salvageable
can't get anything to connect to it
can't get it to reset
can't get it to boot up
lights flash like it's about to
then straight to amber power light
Google r7000 serial recovery. _________________ I am far from a guru, I'm barely a novice.
It took me 5 hours to unbrick my AC1900 v1, and revert before this nightmare.
Ultra short history:
I only have Win10 here. My RS232 to USB is a PL2303HX, it doesn't support Win10 at all! So I was forced to create a Virtual Machine with Win7 just for that. You can imagine. And that was just the beginning!
Code:
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: ... 1669832 bytes read
Entry at 0x00008000
Closing network.
Starting program at 0x00008000
Uncompressing Linux...
I am in the process of checking commits between 40400 and 40439 to see what the possible culprit is, well, I am trying, but svn is choking on it's own vomit.
Starting program at 0x00008000
Uncompressing Linux...
I only have Win10 here. My RS232 to USB is a PL2303HX, it doesn't support Win10 at all!....
SORRY, but that is simply NOT true.
All you have to do is install its old driver on a WIN10 machine.
I rarely use mine but sometimes I stiil do and always have to install the 'Prolific' driver if using the WIN10 computer.
I have the drivers here ---> 'Installing profilic-drivers on Windows 10' ... that was just a part of the 'DD-WRT EA8500' install guide I put up few years back
Last edited by mrjcd on Sat Jul 27, 2019 11:47; edited 1 time in total
now start router and within 10 seconds it will load the file to memory.
now wait and now you can get into openwrt probably trough 192.168.1.1 (in browser) use username root and pw admin and now I could load an old dd-wrt version.