(ftp://ftp.dd-wrt.com/betas/2019/07-12-2019-r40276/broadcom_K3X/) all the names appoint to 40274, is that just a typo and it is really the build 40276, or is the wrong build?
r40274 is the revision of the K3x builds in the r40276 directory
DD-WRT v3.0-r40274 mega (07/12/19)
Linux 3.10.108-d8 #25353 Fri Jul 12 15:40:31 CEST 2019 mips
NO reset -- GUI install over r40260
just used as a WAP.
all working ok
tested on spare RT-N12D1 in 'Repeater' mode
The VAP still does NOT fully start/work after reboot
Router/Version: Cisco Linksys E4200 v1
Firmware: DD-WRT v3.0-r40274 mega (07/12/19)
Kernel: Linux 3.10.108-d8 #25353 Fri Jul 12 15:40:31 CEST 2019 mips
Previous: DD-WRT v3.0-r40189 mega (07/04/19)
Uptime: ~2h 50m
Issues/Errors: Nothing new so far. Looks like the Broadcom K3.x builds were two revision numbers prior, which means the only thing missing was the php updates in r40275 & r40276 commits.
EDIT: I have noticed that the webUI is a little smoother after removing the thread number limitation and adding nanosleep.
Ok, it seems the wi-fi issue has returned and what fixed it on the fly was ipconfig /release, ipconfig /renew... BUT, I had to disconnect and re-connect a few minutes afterwards. I'm trying to figure out why the wi-fi mainly seems to have this problem with dnsmasq renewing dhcp leases, but not wired. I have no connection watchdogs, proxy watchdogs, static leases, or WOL configured. And I am not having these issues in FreshTomato.
Stumbled across this in another build thread:
Router mode, 2.4 at 3610 w 101 beacon, 5 at 3620 w 103 beacon, no keep alive reboot, no SFE.
Down to less than 1 nas/timer event per 24 hours.
I am currently testing the GTK intervals on a fresh reboot without over half of my startup script to see which or if both un-break this problem. Most of the timeouts I had set in startup script were redundant and possibly causing issues.