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: Linksys EA6300
Firmware: DD-WRT v3.0-r40352 std (07/16/19)
Kernel: Linux 4.4.185 #442 SMP PREEMPT Tue Jul 16 12:43:53 CEST 2019 armv7l
Previous: r40260
Mode/Status: Gateway / VAP / Wireguard
Reset: no
Issues/Errors: VAP cann't works, sometime http server crashed, it looks like it's not very stable.
I also test r40276, VAP cann't works too. so I return to r40260 now
Router/Version: Cisco Linksys E4200 v1
File: dd-wrt.v24-40352_NEWD-2_K3.x_mega-e4200.bin
Firmware: DD-WRT v3.0-r40352 mega (07/16/19)
Kernel: Linux 3.10.108-d8 #25413 Tue Jul 16 19:22:58 CEST 2019 mips
Previous: DD-WRT v3.0-r40274 mega (07/12/19)
Reset: No
Mode: Gateway/AP
Uptime: ~6h 32m
Status: OK
Issues/Errors: So far, so good. Will monitor and report issues.
Installed this on my Archer C1900 and my 5ghz wireless became incredibly slow failing to load websites pretty frequently. I reset to defaults to reconfigure everything and when I would save settings / view certain pages on the web interface the web ui would sometimes become unreachable until a power cycle. Went back to the July 4th build and everything works fine.
Router/Version: Buffalo WZR-1750DHP/DHPD Firmware: D-WRT v3.0-r40352 std (07/16/19 Kernel: Linux 4.4.185 #442 SMP PREEMPT Tue Jul 16 12:43:53 CEST 2019 armv7l Previous: BSr40189 which worked good Mode/Status: Gateway / WIFI = AP / Seems ok CPU overclocked to 1400mhz from default 800mhz via r33006 Reset: No Issues/Errors: Laggy and inconsistent UpTime: 00:10:00
This build is wonky on my routers, even the apply settings button at the bottom of the administration page does not respond, the saved and reboot button works though. I went back to r40189 because it worked good.
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Thu Jul 18, 2019 3:24 Post subject:
The only (cosmetic) issue I have noticed so far with this build is using Firefox 68.0 for the webUI. I haven't been using Firefox whatsoever for accessing the webUI in months, so not sure when this issue started. I was not having issues with Safari, Chrome, or Opera that I recall.
The only (cosmetic) issue I have noticed so far with this build is using Firefox 68.0 for the webUI. I haven't been using Firefox whatsoever for accessing the webUI in months, so not sure when this issue started. I was not having issues with Safari, Chrome, or Opera that I recall.
First off....I've lost all my love for Firefox years ago, as it evolved into something it wasn't...¯\(°_o)/¯
Second....I am almost as anti google as I am anti apple....It's a business practice, privacy thing ¯\_(ツ)_/¯
Could this issue have something to do with the browser zoomed in 150%?
Seams strange that you have no width scroll bar for being zoomed in that much.
Is it zoomed the same in all the other browsers you use that you say are ok? _________________ Location 1
R7800- DD-WRT v3.0-r53562 (10/03/23) Gateway
WNDR3400v1 DD-WRT v3.0-r35531_mega-nv64k (03/26/18 ) Access Point
WRT160Nv3 DD-WRT ?v3?.0-r35531 mini (03/26/18 ) Access Point
WRT54GSv5 DD-WRT v24-r33555_micro_generic (10/20/17) Repeater
Location 2
R7800- DD-WRT v3.0-r51855 (02/25/23) Gateway
R6300v2- DD-WRT v3.0-r50671 (10-26-22) Access Point
WNDR3700v2 DD-WRT v3.0-r35531 std (03/26/18 ) Access Point
E1200 v2 DD-WRT v3.0-r35531 mega-nv64k (03/26/18 ) Gateway(for trivial reasons)
RBWAPG-5HACT2HND-BE RouterOS-v6.46.4 (2/21/20) Outdoor Access Point
2x RBSXTG-5HPACD RouterOS-v6.46.4 (2/21/20) PTP Bridge 866.6Mbps-1GbpsLAN
Location 3
2x R7000- DD-WRT v3.0-r50671 (10/26/22) Access Points
2x RBWAPG-60AD RouterOS-v6.45.9 (04/30/20) PTP Bridge 2.3Gbps-1GbpsLAN
2x RBSXTsqG-5acD RouterOS-v6.49.7 (10/14/22) PTP Bridge 866.6Mbps-1GbpsLAN Thank You BrainSlayer for ALL that you do & have done, also to "most" everyone here that shares their knowledge
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Thu Jul 18, 2019 21:42 Post subject:
Dr_K wrote:
kernel-panic69 wrote:
The only (cosmetic) issue I have noticed so far with this build is using Firefox 68.0 for the webUI. I haven't been using Firefox whatsoever for accessing the webUI in months, so not sure when this issue started. I was not having issues with Safari, Chrome, or Opera that I recall.
First off....I've lost all my love for Firefox years ago, as it evolved into something it wasn't...¯\(°_o)/¯
Second....I am almost as anti google as I am anti apple....It's a business practice, privacy thing ¯\_(ツ)_/¯
Could this issue have something to do with the browser zoomed in 150%?
Seams strange that you have no width scroll bar for being zoomed in that much.
Is it zoomed the same in all the other browsers you use that you say are ok?
Zoom percentage and size of window make no difference, no matter which browser. Firefox just seems to not be loading the pages correctly now. Also don't have a width scroll bar on any other browser at 150% zoom. It's only when the white area of the page exceeds window width...
Router/Version: Asus RT-N66W
File: DD-WRT v3.0-r40352 big (07/16/19) (BS)
Kernel: Linux DD-WRT 3.10.108-d8 #25409 Tue Jul 16 19:18:48 CEST 2019 mips DD-WRT
Mode: Gateway
Status: Clean install, QoS, DHCP Auto, Entware, nothing fancy installed, unit up for 23 hours, minor bug/problem
Simply put, router can't get a WAN IP after a reboot. There are 2 workarounds that both do the same thing (restart wan) I believe.
a) Log in to web GUI and hit "Apply Settings" under
Code:
Setup > Basic Setup
or
Administration > Management
b) Add those commands to Startup (or run manually after reboot is complete)
Code:
sleep 30 (just to be sure)
stopservice wan
sleep 3
startservice wan
I think problem lies around wan service starting up too early, before some necessary services kick in, getting 0.0.0.0 as WAN IP (or not getting an IP at all) and never checking it again. However I'm not a networking or coding expert, am just a geek loves to play around with his router so what do I know
Thanks for replying! I've visited several threads and svn links by people having the same/similar problem, and yes, it seems like an ASUS-specific bug. What do you suggest as the next step? Should I submit it to SVN as a new ticket/necro an existing one(not same but seems similar to a degree) or posting here is just enough?