Posted: Mon Sep 20, 2021 12:20 Post subject: New Build - 09/20/2021 - r47474
[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the risks involved and device specificrecovery methods.
Avoid discussions! Create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
Issues, observations, and/or workarounds reported:
• DNScrypt 1.95 can still be used in the GUI, but v2 (not compatible) requires Golang and thus Entware. #6246
• WDS does not work on Broadcom ARM devices(only MIPS<->MIPS) & bridge modes on k4.4 devices may sometimes work
in some configurations for certain builds but are not supported by the bcmdhd driver. Use client or repeater instead.
• VAPs not working at bootfixed for unbridged VAPs in40562 - 40566. Effective startup commandsdiscussion thread is here.
• If start-up scripts do not work from USB add a delay, e.g. wait script or 'sleep 25'.
• Broadcom ARM devices if 5 GHz channels are missing, via Telnet/SSH: 'nvram set brcm_unlock=1' 'nvram commit' 'reboot'
• Show us your findings with steps to reproduce, configuration, output, logs and important information below!
Important:
• For issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog, klog, serial, strace, tcpdump, wireshark etc.
• Any firewall NAT or WAN issues, show output: 'iptables -vnL', 'iptables -t nat -vnL', 'iptables -t mangle -vnL' and /tmp/.ipt file.
• Search SVN tickets & discuss in forum before opening. Before reporting: reset & manually set up, not restore from a backup.
• Please include operating & wireless modes (e.g. Gateway, Router, AP, CB, WDS, Mesh) & relevant configuration information.
Upgraded: from DD-WRT v3.0-r47033 std (07/08/21)via telnet (update via GUI not possible because nvram is placed on linux partition and not linux2 partition due to Xvortex CFE)
Reset: No not this time
Configuration: AP, DHCP server, 2,4GHz wireless running, 5GHz running, some static leases and some port range forwarding, NVRAM size just over 32K (NVRAM size should not be a problem with the Xvortex CFE)
Router/Version: Netgear R6250
Firmware: DD-WRT v3.0-r47474 std (09/20/21)
Kernel: Linux 4.4.283 #4096 SMP Mon Sep 20 05:45:13 +07 2021 armv7l
Mode: Gateway, Wireless AP, unbound & CTF & FA Enabled. NAT/QoS Off
Reset: No, not this time
Previous : r47381
Upgrade: Web and 1st succeed without reset.
Temperatures CPU 75.2 °C / WL0 shutdown /WL1 55.8 °C
Load: 0.18, 0.06, 0.01
Uptime 2h30m
Errors: No, not at this moment. Merci!
Router/Version: Netgear R7000
File: netgear-r7000-webflash.bin
Firmware: DD-WRT v3.0-r47474 std (09/20/21) (prev. DD-WRT v3.0-r47282 std (08/30/21))
Kernel: Linux 4.4.283 #4096 SMP Mon Sep 20 05:45:13 +07 2021 armv7l
Mode: Gateway, Wifi disabled, Wireguard for external access, WAN to DSL, Keep Alive reboot 5:00 in the morning
Reset: No
Status: Ok, up 1:24h.
Router/Version: Asus RT-N66U
File: dd-wrt.v24-47474_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r47474 big (09/20/21) (prev. DD-WRT v3.0-r47282 big (08/30/21))
Kernel: Linux 4.4.283 #11954 Mon Sep 20 08:48:36 +07 2021 mips
Mode: Gateway, Wifi disabled, WAN disabled, Wireguard Endpoint for external VPS, connected via LAN to R7800, Keep Alive reboot 6:05 in the morning
Reset: No
Status: Ok, up 1:24h.
Linksys E2500
DD-WRT v3.0-r47474 mega (09/20/21)
Linux 4.4.283 #11958 Mon Sep 20 08:53:15 +07 2021 mips
GUI install over r47461
'dd-wrt.v24-47474_NEWD-2_K3.x_mega.bin'
used as a simple WAP
all very good -- uptime 14:27
###
The Asus RT-N12D1 did NOT fare so well
In the wee hours last night using its webif I installed r47474 over working r47461 that hasn't been reset in long time
Could NOT reach it after that...ssh even said it was unreponsive. Could access devices behind it so ports were still alive.
Dad called before daylight saying internet was NOT working there. I went to see what all was broken and the RT-N12D1 was about as dead as it could get.
Only its switch ports were still alive.
Power cycle did NOTHING this time so I swapped it out with what was used for many years
Netgear WNR2000v3
DD-WRT v3.0-r43845 std (07/18/20)
Linux 3.10.108-d10 #52834 Sat Jul 18 05:21:53 +04 2020 mips
It already had the correct conf & its MAC/name is still in main router DCHP leases so all is good for them again
Had to recover the ASUS. Also it will soft brick if you do a reset with any either of the last two previous releases.
Doing recovery on the stupid thing a few times really is a PITA.
I don't think BS ever had this device and it has always shown as an Asus RT-N12B running DD-WRT
ASUS RTN12D1 stuff
In the wee hours last night using its webif I installed r47474 over working r47461 that hasn't been reset in long time
Could NOT reach it after that...ssh even said it was unresponsive. Could access devices behind it so ports were still alive.
I updated my old WRT54GL last night to 47474 nokaid (as a backup for my sis' house*) to see if the latest builds worked. Lost access after the flash, but after resetting (which seemed to be finicky too) I got into the GUI. However, after setting it up as a Client Bridge I lost GUI and telnet access; no ping either. The Switch Config page is all messed up; see pic. Reset and tried AP mode too; same thing.
I reset and reverted to 46640 (which actually came up as 46412, that was before the 46454 bcm swconfig changes) and was fine. And it's Switch Config page is normal.
*Good thing I didn't update my sis' WRT54 AP's over the weekend. My nephew had reset one and messed everything up. They have schitty slow DSL with no neighbors, so they don't need anything faster/newer.
I pinged Sebastian about it, but he's busy w/ other things atm to investigate. I'm in no hurry... at all. B-)
I have been meaning to address this and get the proper information to BS so you don't have to muck with it like this. I thought perhaps the file could be hexedited, or that burnboardid could be done; but a proper port would be more beneficial. Both the v1 and v2 are still TBD because donated hardware was never sent. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I pinged Sebastian about it, but he's busy w/ other things atm to investigate. I'm in no hurry... at all. B-)
Surprised you are still messing with the old things...
I still have three running within my net 24/7 but I quit any firmware stuff on them long while back & put old reliable FW that works for me.
WRT54Gv2 (r35531) WDS to WAP54Gv3 (r35531) wired to WRT54Gv8 (r33555) AP an ain't nobody hacked into it yet and iffin they did I would prolly know about fairly quick and just kill it. The WDS link is on ch 14 so ain't anybody here I know of can even see that. 'bout same as my many years old WDS link with the two E2100 between my place & the folks...E2100s WDS is on ch 13 way up in the air so it never interfers with the ch 14 between their house & shop down fairly low.
Thanks--glad you told BS... every lil bit helps iffin he get around to it.
Surprised you are still messing with the old things...
Well, the last build on it was from Feb 2020. Though my sis' WRT's have a 11/20 build...
So another weekend investigation was my parents' N66U AP (bcasting via ICS from their Win10 Verizon cellular USB internet) quit working. Resetting had no effect, and plugging in power immediately lit up 3 LED's that never flashed/changed... seemed like a goner. Note: this had a WAN and (1 or 2) LAN ports damaged by lightning years ago. So I had little hope for it.
This evening I took it apart to check for issues (and test the caps) and forgot it had a factory serial header (and labelled! crazy.), so figured I'd see what (if anything) it was doing. Lots of 'can't read nvram' sorta errors. Broke CFE, `nvram erase`, and boom! Back into AsusWRT-Merlin... which is long unsupported for the N66U so I put 47474-big on it. As usual for the past couple years, I had lots of trouble getting a web browser to talk to it after a reset (FF/Edge/IE/Netsurf/Epiphany) but finally got it set up as an AP and working. Yay me. \o/
Anyone still awake?
Router/Version: Asus RT-N66U B1 (1.0.1.9 CFE)
File/Kernel: N66U big / Linux 4.4.283 #11954 Mon Sep 20 08:48:36 +07 2021 mips
Previous/Reset: AsusWRT-Merlin / oh ya, all kinds of resets
Mode/Status: AP
After I was done, swconfig shows VLAN 1: 0 1 2 3 4 8t
However, the Switch Config tab is still all crazy (see below). And before setting up as AP that page had all the checkboxes blank. I see BS made a SwCfg change for bcm today.
Router/Version: Linksys EA6900
File: linksys-ea6900-webflash.bin
Firmware: Firmware: DD-WRT v3.0-r47474 std (09/20/21)
Kernel: Linux 4.4.283 #4096 SMP Mon Sep 20 05:45:13 +07 2021 armv7l
Mode: Gateway, Wifi, WAN to DSL, Keep Alive reboot 2:00 Thu, Startup script -> WOL on demand
Reset: No
Status: The startup script dies. It runs for a few hours and dies. I ran it manually with nohup and the output is:
root@BatRouter:~# cat nohup.out
Killed
root@BatRouter:~#