Posted: Mon Feb 20, 2023 9:41 Post subject: New Build - 02/20/2023 - r51787
Welcome to Marvell r51787 beta release thread for reporting, feedback to developers and community benefit.
Please do not flash builds until installation is understood, risks involved and device specificrecovery methods.
Avoid discussions, create threads for questions, general problems or use search; this thread is not for support.
List router model & version or revision, operating & wireless modes & exact filename/firmware image flashed.
CLI Flash: 'cd /tmp' then 'wget {file URL}' (httponly) or 'curl -O {file URL}' (http, https, ftp). 'write {file} linux' then 'reboot'.
Issues, observations, and/or workarounds reported:
• WebUI: Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.
• Please report findings with steps needed to reproduce, configuration, clients, output, logs and important information below!
Important:
• Detail issues & relevant configs, logs: syslog klog 'dmesg' 'cat /tmp/var/log/messages' nvram set console_debug=1, serial.
• Firewall NAT: 'iptables -vnL' 'iptables -t nat -vnL' 'iptables -t mangle -vnL' & 'cat /tmp/.ipt'. Misc: stracetcpdumpwireshark.
• Gremlins: reboot. cold boot. Reset & reconfigure not restore backup. Search Trac & discuss in forum before opening tickets.
• Include operating & wireless modes (e.g. Gateway, Router, AP, SB, WDS, Mesh) and applicable configurations to reproduce.
root@WRT1900ACSv1:/tmp# curl https://download1.dd-wrt.com/dd-wrtv2/downloads/bet
as/2023/02-20-2023-r51787/linksys-wrt1900acs/ddwrt-linksys-wrt1900acs-webflash.b
in -o webflash-ACSv1.bin
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (60) SSL certificate problem: certificate has expired
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
root@WRT1900ACSv1:/tmp#
_________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
DD-WRT Router Model Linksys WRT1900ACS v2
Firmware Version DD-WRT v3.0-r51787 std (02/20/23)
Kernel Version Linux 4.9.337 #3645 SMP Mon Feb 20 06:03:07 +07 2023 armv7l
Current Time Tue, 21 Feb 2023 08:02:24
Uptime 15 h
update-browser waterfox, I switched from partition 2, Firmware Version v3.0-r51741, all ok
connection Type PPPoE - IPv6 Type DHCPv6 with Prefix Delegation 1Gbps
IPv6 Type DHCPv6 with Prefix Delegation-On - Ok
Operating Mode Gateway/AP
Shortcut Forwarding Engine-On
Schedule Reboot-On,
Web Access Protocol - HTTPS,
SSH (public key)-ok
Validate DNS Replies (DNSSEC)-ok
Port Forwarding - Ok,
USB - System Log -Ok
Schedule Reboot - At a Set Time - On
Wireless Interface 5GHz-Wireless Mode AP-Wireless Network Mode-AC/N, Width VHT 80 Mhz-Wireless Channel-36,Short GI, Short Preamble, Single User Beamforming, Radio Scheduling, Enable-WPA2 Personal-CCMP-128 (AES), Regulatory Domain Romania , all-ok
Wireless Interface 2.4GHz-Wireless Mode AP-Wireless Network Mode-N, Width VHT 40 Mhz-Wireless Channel-6, Extension Channel Lower,Short Preamble, Short GI , Radio Scheduling, Enable-WPA2 Personal-CCMP-128 (AES) all-ok!
After configuring the settings, I rebooted the router every time![/quote] _________________ Internet provider https://en.wikipedia.org/wiki/RCS_%26_RDS 1Gbps
WDR3600 rev.1.5 - DD-Wrt
Linksys WRT1900ACS v.2 DD-Wrt/-OpenWrt
The secondary partition from where I made the transition to the new version I did a factory reset, now I noticed that it receives the settings from the new version, it is active?
DD-wrt behaves like the linksys firmware, only there I saw this thing... _________________ Internet provider https://en.wikipedia.org/wiki/RCS_%26_RDS 1Gbps
WDR3600 rev.1.5 - DD-Wrt
Linksys WRT1900ACS v.2 DD-Wrt/-OpenWrt
The secondary partition from where I made the transition to the new version I did a factory reset, now I noticed that it receives the settings from the new version, it is active?
DD-wrt behaves like the linksys firmware, only there I saw this thing...
Did you actually mean a "factory reset" (e.g., reset pin) or an NVRAM reset (e.g., from the GUI)? I didn't do any reset, but my CLI firmware (f/w) upgrade went normally. My older f/w was in boot_part 1, and the new f/w went into boot_part 2 as expected.
EDIT: If I recall correctly, a single copy of NVRAM variables applies equally to both boot partitions. _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
Last edited by o2bad455 on Tue Feb 21, 2023 15:08; edited 3 times in total
Router/Version: Linksys WRT1900ACS v1 / DD-WRT v3.0-r51787 std (02/20/23)
File/Kernel: CLI webflash / Linux 4.9.337 #3645 SMP Mon Feb 20 06:03:07 +07 2023 armv7l
Previous/Reset: r51440 / No
Mode/Status: Gateway, DNSmasq, OpenVPN Client, FreeRADIUS Server, VLANs, VAPs, WPA3, Radar Detection (DFS), 14 dBm, AutoChannel / Uptime 8:04
Issues/Errors: I finally got DNSMasq working again by replacing an NTP pool name (after trying several) with a single NTP server's IP address. I don't like relying on a single NTP IP, but at least it's working for now. NTP names, and therefore DNSMasq resolution, seemed to have stopped working for my setup somewhere between r49681 and r51440. I was not and am not using Unbound. Everything else is working like clockwork, thanks! _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
The secondary partition from where I made the transition to the new version I did a factory reset, now I noticed that it receives the settings from the new version, it is active?
DD-wrt behaves like the linksys firmware, only there I saw this thing...
Did you actually mean a "factory reset" (e.g., reset pin) or an NVRAM reset (e.g., from the GUI)? I didn't do any reset, but my CLI firmware (f/w) upgrade went normally. My older f/w was in boot_part 1, and the new f/w went into boot_part 2 as expected.
EDIT: If I recall correctly, a single copy of NVRAM variables applies equally to both boot partitions.
The idea was as follows, before switching to r51787 I did a Restore to Factory Defaults to r51741 from NVRAM Settings!
Today I said let's see how the return to the old version behaves, when I have r51741 I noticed that I have the settings from r51787!
It is normal for this to happen, knowing that before the update I did a Restore to Factory Defaults? _________________ Internet provider https://en.wikipedia.org/wiki/RCS_%26_RDS 1Gbps
WDR3600 rev.1.5 - DD-Wrt
Linksys WRT1900ACS v.2 DD-Wrt/-OpenWrt
Upgrade to this version brick the router Netgear r7000. It works after a factory reset, but it's impossible to restore the configuration from a copy, because that also brick the router.
Back to the previous version of r51741 (02-18-2023) and everything works. Something is wrong with version r51787 (02-20-2023) for this router.
Router/Version: Netgear R7000
File/Kernel: Linux 4.4.302-st37 #8694 SMP Sat Feb 18 03:53:47 +06 2023 armv7l
Previous/Reset: r51741/No
Mode/Status: Gateway & SFE:on & STP:off, DNSmasq, Tunels & WireGuard & PBR sources via WAN, Wireless:2,4/5 GHz & WPA2-PSK & Virtual, Use NVRAM for Client Lease DB, Encrypt DNS, Firewall:on, Port Forwarding, QoS
Issues/Errors: Bricked after update from r51741 to r51787. After rebooting after the update, not all the normal LEDs light up and no communication with the router.
UPDATE
After disabling the option: Shortcut Forwarding Engine, Use NVRAM for Client Lease DB, QoS and upgrade to firmware r51838, the router upgraded correctly. So, it looks like something has changed above version r51741 (i.e.: r51787 and r51838) that affects any of the above-mentioned options and causes the router's inability to boot properly (if a reset to factory settings was not selected during the upgrade).
Last edited by iTeth on Fri Feb 24, 2023 14:30; edited 2 times in total
Upgrade to this version brick the router Netgear r7000. It works after a factory reset, but it's impossible to restore the configuration from a copy, because that also brick the router.
I didn't want to use a backup copy, I just wanted to see if the command to return to the previous partition works, which was already reset to the default values without settings!
Code:
"ubootenv get boot_part - 1,2 - show me the partition you are on (2,1)!!!!
ubootenv set boot_part 1 or 2 - choose the partition you want to boot (1.2)!!!!
Upgrade to this version brick the router Netgear r7000.
This thread is for Marvell chips. The Netgear R7000 uses a Broadcom chip, so you should probably post your results there. See https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=334070 _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
The idea was as follows, before switching to r51787 I did a Restore to Factory Defaults to r51741 from NVRAM Settings!
Today I said let's see how the return to the old version behaves, when I have r51741 I noticed that I have the settings from r51787!
It is normal for this to happen, knowing that before the update I did a Restore to Factory Defaults?
I think that is normal since there is only one copy of the NVRAM variables for DD-WRT, even for routers with multiple boot partitions. That is, without extra unload/reload of NVRAM, the same NVRAM variables apply to both partitions.
After you did the reset on the old build in one partition, you used the new build in the other partition, right? Assuming you entered any new settings (no matter from scratch or from backup) for the new build, those would be saved in NVRAM and get read and used when booting from either partition.
If you did not change anything, then it seems like the reset must have failed (which I have seen happen occasionally - possibly due to browser issues - another reason I refer CLI). To know if that was it, you would have had to verify the reset to defaults before changing anything in NVRAM from either partition.
At least that is how I understand the default behavior for DD-WRT. The only time that I have seen different behaviour (that is, settings specific to partition) is when experimenting with completely different firmwares that must have stored their setup variables elsewhere. _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
so far after i loaded this firmware ive only noticed that i didnt wake up filthy rich or anything. _________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.