Beta Build 41212: 09-30-2019-r41212

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2  Next
Author Message
flyzipper
DD-WRT User


Joined: 21 Feb 2016
Posts: 294

PostPosted: Mon Sep 30, 2019 20:12    Post subject: Beta Build 41212: 09-30-2019-r41212 Reply with quote
Downloads: (if a link does not work, try another)
https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2019/09-30-2019-r41212/
ftp://ftp.dd-wrt.com/betas/2019/09-30-2019-r41212/
Alternate link: DD-WRT website
Note: for wget (or curl) with CLI flash (`write {f/w} linux`), change the https to http, use `curl -k {link} -o {file}`, or use ftp

Changelogs:
SVN* changelog since last build: 41174
Summary: (deprecated after 29739)
*Github mirror: https://github.com/mirror/dd-wrt/

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 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. PBR/UDP with SFE working again since r40513 (see 6729)
5. CAKE scheduler changes "completed" with r41057 (see 5796) & FQ_CODEL_FAST with r41027 (reset first!)
6. Reset button was broken in 40571; fixed in build 40750.

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 fixed (only for unbridged VAPs?) with r40564:40566...

Important: if reporting any issues, provide applicable info (GUI syslog, `dmesg`, `cat /var/log/messages`, etc.)
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.):
Code:
[b]Router/Version: [/b]
[b]File: [/b]
[b]Kernel: [/b]
[b]Mode: [/b]
[b]Status: [/b]

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.[/quote]
Sponsor
flyzipper
DD-WRT User


Joined: 21 Feb 2016
Posts: 294

PostPosted: Mon Sep 30, 2019 20:15    Post subject: Reply with quote
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r41212 std (09/30/19)
Kernel: Linux 4.4.194 #5 SMP Sun Sep 29 22:25:07 +04 2019 armv7l
Previous: r41174
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Working well so far.

Uptime: 2hrs 28min
Temperatures: CPU 72.5 °C / WL0 49.3 °C / WL1 55.2 °C
turbowells
DD-WRT Novice


Joined: 14 Sep 2019
Posts: 44
Location: Maine, USA

PostPosted: Mon Sep 30, 2019 20:37    Post subject: Reply with quote
Router/Version: Asus RT-N66U
File: dd-wrt.v24-41212_NEWD-2_K3.x_mega_RT-N66U.trx
Kernel: Linux 3.10.108-d8 #20 Mon Sep 30 16:54:37 +04 2019 mips
Mode: AP w/USB
Previous: r41174
Reset?: N
Status: Working

Router/Version: Asus RT-N12D
File: dd-wrt.v24-41212_NEWD-2_K3.x_mega.bin
Kernel: Linux 3.10.108-d8 #20 Mon Sep 30 16:54:37 +04 2019 mips
Mode: AP
Previous: r41174
Reset?: N
Status: Working

Upgraded via gui. Syslogs clean. Up 90 minutes. We'll see if the rekey issue reappears.
tinkeruntilitworks
DD-WRT User


Joined: 21 May 2019
Posts: 129

PostPosted: Mon Sep 30, 2019 21:12    Post subject: Reply with quote
Router: Netgear R7000P
Kernel: Linux 4.4.194 #10 SMP Mon Sep 30 10:51:40 +04 2019 armv7l
Mode: Gateway / AP / Unbound
Reset: Yes
Uptime: 2hrs
Status: all seems well
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 2317
Location: Texas, USA

PostPosted: Tue Oct 01, 2019 10:37    Post subject: Cisco Linksys E4200 v1 Reply with quote
Router Model / Version: Cisco Linksys E4200 v1
File: dd-wrt.v24-41212_NEWD-2_K3.x_mega-e4200.bin
Firmware: DD-WRT v3.0-r41212 mega (09/30/19)
Kernel: Linux 3.10.108-d8 #20 Mon Sep 30 16:54:37 +04 2019 mips
Previous: DD-WRT v3.0-r41174 mega (09/26/19)
Reset: No
Mode: Gateway / AP - QoS (HFSC+FQ_CODEL_FAST)
Uptime: ~ 6:20
Status: OK
Issues / Errors: Nothing new to report, although I just noticed that the kernel compile # has apparently been reset.
twindragon6
DD-WRT User


Joined: 29 Jun 2008
Posts: 67

PostPosted: Tue Oct 01, 2019 13:24    Post subject: Netgear Nighthawk R7000 Reply with quote
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r41212 std (09/30/19)
Kernel: Linux 4.4.194 #5 SMP Sun Sep 29 22:25:07 +04 2019 armv7l
Mode: Gateway
Reset: No
Previous: 09-26-2019-r41174
Status: Working



Logs.txt
 Description:
Logs

Download
 Filename:  Logs.txt
 Filesize:  119.65 KB
 Downloaded:  52 Time(s)

PeteSL
DD-WRT Novice


Joined: 01 May 2007
Posts: 49

PostPosted: Tue Oct 01, 2019 18:47    Post subject: Reply with quote
Router/Version: Asus RT-AC3100
File: asus_rt-ac3100-firmware.trx
Kernel: Linux 4.4.194 #10 SMP Mon Sep 30 10:51:40 +04 2019 armv7l
Mode: Gateway/AP/OpenVPN Client
Status: Running

Been up for 8 hours. Seems to be functioning correctly. No obvious issues.
Veritech
DD-WRT User


Joined: 02 Jan 2007
Posts: 112

PostPosted: Tue Oct 01, 2019 23:43    Post subject: WNDR4500v2 RT-N66R Reply with quote
Router/Version: WNDR4500v2
File: DD-WRT v3.0-r41212 giga (09/30/19)
Kernel: Linux 3.10.108-d8 #4 Mon Sep 30 16:34:06 +04 2019 mips
Mode: AP/Switch/DHCP Forwarder
Status: Working
Uptime: 1 day, 25 min
Previous: 41074
Temps: WL0 44.2 °C / WL1 46.0 °C (heatsink mod)
The WNDR4500v2 was bricked on update with radios on or off. Required flashing stock, 30 second reset, then reconfigure. Version 36247 was the last version that did not require JTAG or tftp recovery.

Router/Version: RT-N66R
File: DD-WRT v3.0-r41212 big (09/30/19)
Kernel: Linux 3.10.108-d8 #16 Mon Sep 30 16:48:40 +04 2019 mips
Mode: AP/Switch/DHCP Forwarder
Status: Working
Uptime: 1 day, 40 min
Previous: 41027
Temps: WL0 52.5 °C / WL1 51.4 °C

RT-N66R flashed with no issue. Reboot was only a couple of minutes before fully functional.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2356
Location: Indy

PostPosted: Wed Oct 02, 2019 2:16    Post subject: Re: WNDR4500v2 RT-N66R Reply with quote
Veritech wrote:
The WNDR4500v2 was bricked on update with radios on or off. Required flashing stock, 30 second reset, then reconfigure. Version 36247 was the last version that did not require JTAG or tftp recovery.
Have you a flash/boot log? That's the only way to help BS find the issue.
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 19.7.5|EA6900v1.1@1GHz, F7D8302 FT2019.3b|DD 41218: WNDR4500v2, WNDR4000@533, E1500@353,
E2500, R6300v1, WRT54*@250: GLv1.1 nsg, GSv6 µ
|RT-N66U@663 Merlin 380.70|OEM: WGR614v10@400-WNR1000v3 mod
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 2317
Location: Texas, USA

PostPosted: Wed Oct 02, 2019 4:52    Post subject: Re: WNDR4500v2 RT-N66R Reply with quote
jwh7 wrote:
Veritech wrote:
The WNDR4500v2 was bricked on update with radios on or off. Required flashing stock, 30 second reset, then reconfigure. Version 36247 was the last version that did not require JTAG or tftp recovery.
Have you a flash/boot log? That's the only way to help BS find the issue.


This is why I flash with serial console connected and up anymore. After that first brick, it's just easier to know if it's gonna require recovery. If you don't want to crack open the router to connect, you can do a mod that uses a 3.5mm (1/8") stereo jack and plug for your interconnect cable for the adapter. Only thing I suggest is that if you have multiple devices, make sure the internal side of said mod connects correctly so you can use a standard config on the external cable. Single-pair STP audio snake cable works great.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2356
Location: Indy

PostPosted: Wed Oct 02, 2019 19:32    Post subject: Re: WNDR4500v2 RT-N66R Reply with quote
kernel-panic69 wrote:
jwh7 wrote:
Veritech wrote:
The WNDR4500v2 was bricked on update with radios on or off. Required flashing stock, 30 second reset, then reconfigure. Version 36247 was the last version that did not require JTAG or tftp recovery.
Have you a flash/boot log? That's the only way to help BS find the issue.
This is why I flash with serial console connected and up anymore. After that first brick, it's just easier to know if it's gonna require recovery.
"Hmm," I thought, "I'm sure my 4500v2 is currently newer than 36247"...

Yup I was on 40559, then upgraded to 41218 just fine from the GUI. Confused Same size as 41212, so definitely need a serial log; maybe a NAND issue or configuration interaction anomaly. One thought; do you use the "After flashing, reset to: Reset to Default settings" option? I never do, as it caused issues in the past.

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 19.7.5|EA6900v1.1@1GHz, F7D8302 FT2019.3b|DD 41218: WNDR4500v2, WNDR4000@533, E1500@353,
E2500, R6300v1, WRT54*@250: GLv1.1 nsg, GSv6 µ
|RT-N66U@663 Merlin 380.70|OEM: WGR614v10@400-WNR1000v3 mod
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 2317
Location: Texas, USA

PostPosted: Thu Oct 03, 2019 3:44    Post subject: Re: WNDR4500v2 RT-N66R Reply with quote
jwh7 wrote:
"Hmm," I thought, "I'm sure my 4500v2 is currently newer than 36247"...

Yup I was on 40559, then upgraded to 41218 just fine from the GUI. Confused Same size as 41212, so definitely need a serial log; maybe a NAND issue or configuration interaction anomaly. One thought; do you use the "After flashing, reset to: Reset to Default settings" option? I never do, as it caused issues in the past.


https://svn.dd-wrt.com/ticket/6401 <-- it's been crashing httpd since 36168 when 'reset to defaults' was selected when upgrading here. I haven't tested it in a while, but it's basically a 'soft brick'. Power cycle the device and re-configure manually and you're done. Just don't jump the gun and really brick it Wink
Veritech
DD-WRT User


Joined: 02 Jan 2007
Posts: 112

PostPosted: Fri Oct 04, 2019 3:29    Post subject: Re: WNDR4500v2 RT-N66R Reply with quote
jwh7 wrote:
kernel-panic69 wrote:
jwh7 wrote:
Veritech wrote:
The WNDR4500v2 was bricked on update with radios on or off. Required flashing stock, 30 second reset, then reconfigure. Version 36247 was the last version that did not require JTAG or tftp recovery.
Have you a flash/boot log? That's the only way to help BS find the issue.
This is why I flash with serial console connected and up anymore. After that first brick, it's just easier to know if it's gonna require recovery.
"Hmm," I thought, "I'm sure my 4500v2 is currently newer than 36247"...

Yup I was on 40559, then upgraded to 41218 just fine from the GUI. Confused Same size as 41212, so definitely need a serial log; maybe a NAND issue or configuration interaction anomaly. One thought; do you use the "After flashing, reset to: Reset to Default settings" option? I never do, as it caused issues in the past.


Doing the jtag and watching the boot process/upgrade output I have done previously but I watched for it to lock. I didn't copy the output. Doing the debug and collection of the data is new to me so bare with me if I'm unsure what/how to collect. Do we need a console copy and past when the update is applied? I only purchase routers that are supported by dd-wrt so I want to give back what I can to improve the experience.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2356
Location: Indy

PostPosted: Fri Oct 04, 2019 16:35    Post subject: Re: WNDR4500v2 RT-N66R Reply with quote
Veritech wrote:
Do we need a console copy and past when the update is applied?
Yes Smile

Are you using JTAG or serial?

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
x64 OPNsense 19.7.5|EA6900v1.1@1GHz, F7D8302 FT2019.3b|DD 41218: WNDR4500v2, WNDR4000@533, E1500@353,
E2500, R6300v1, WRT54*@250: GLv1.1 nsg, GSv6 µ
|RT-N66U@663 Merlin 380.70|OEM: WGR614v10@400-WNR1000v3 mod
Veritech
DD-WRT User


Joined: 02 Jan 2007
Posts: 112

PostPosted: Sat Oct 05, 2019 3:42    Post subject: Re: WNDR4500v2 RT-N66R Reply with quote
jwh7 wrote:
Veritech wrote:
Do we need a console copy and past when the update is applied?
Yes Smile

Are you using JTAG or serial?


I'm using the TTL Serial adapter, I'm familiar with old school serial connections on the DB9 ports but I'm not sure if this is considered JTAG or just a slightly different serial connection. Standard serial port shows gibberish when connected. I'll connect it here soon and get a capture of the output.
Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum