Posted: Mon Oct 13, 2025 8:01 Post subject: New Build - 10/13/2025 - r62324
Welcome to Marvell r62324 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'. Debug Analyze: stracetcpdump.
• 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.
Router/Version: 1900ACv1
File/Kernel: 62324
Previous/Reset: 59045/Factory Reset
Mode/Status: AP
Issues/Errors: No WAN access w/SFE on or off. Back to 59045.
Update method: CLI / SSH flash from konsole over wireless
Router/Version: Linksys WRT32X
File/Kernel: ddwrt-linksys-wrt32x-webflash.bin / Linux 6.1.155-rt28 #175 SMP Mon Oct 13 02:56:10 +07 2025 armv7l
Previous/Reset: 61848 / No, last reset at 61848
Mode/Status: Gateway, AP, PPPoE, SFE enabled, WAN to ONT, ignore WAN DNS, non-default router IP, SmartDNS for DoT (single host, dualstack IP enabled), DDNS (TLS enabled), wireguard server (preshared key, non-default port), SSHD (public key only, non-default port), telnet disabled, no VAP, wlan0 5GHz VHT80 AC only, wlan1 2.4GHz HT20 N only, wlan2 disabled, WPA2 Personal CCMP-128 all radios / Working
Issues/Errors:
Router initially could not get WAN IP via PPPoE with SFE enabled. Had to disable SFE, save and reboot, re-enable SFE, save and reboot, in order to get WAN IP via PPPoE with SFE enabled. Separately, had a one-off UI glitch after navigating to Administration tab, but have not been able to reproduce. Have not been able to replicate the httpd crash that some Atheros users have observed when navigating to the wireless tab, but will keep monitoring.
Router/Version: 1900ACv1
File/Kernel: 62324
Previous/Reset: 59045/Factory Reset
Mode/Status: AP
Issues/Errors: No WAN access w/SFE on or off. Back to 59045.
Can anyone else with 1900ACv1 get this to work?
I upgraded mine days ago with r62192 straight from r57956. I noticed the load average going to the roof, both cpus at %100 but stabilized after a couple of reboots + I unchecked a few boxes under the new security tab especially all the limit checkboxes and detect port scanners as I found out here
These new versions I always flash w/factory defaults, enter a new password (and nothing else changed in settings), and then test with a wired client.
I see a bunch of 'undefined' labels on the Security tab, Backup tab, etc. Applying settings and rebooting does not fix that.
I have also tried flashing the new versions to my working 59045 setup WITHOUT resetting to factory defaults (SFE is disabled in this case) and I have the same issue...I get a WAN IP, but no traffic is sent out to the WAN.
Joined: 08 May 2018 Posts: 16498 Location: Texas, USA
Posted: Thu Oct 16, 2025 1:49 Post subject:
CTRL+F5 or clear your browser cache or reload the page. This problem usually fixes itself when you're using a portable browser in private browsing mode by just a reload of the page. Resetting to defaults is pointless unless there are problems, because most nvram variable changes are handled automatically in the source code. While there may be cruft and anomalies that occur, a reset isn't always necessary when upgrading. _________________ "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... RSS feed for DD-WRT releases (2025) RSS feed for DD-WRT releases (2024) RSS feed for DD-WRT releases (2023)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I remember the standard approach here was that, with each new version, you should reset to factory defaults and then manually reconfigure everything...when did that change?
But, as I said, upgrading without resetting doesn't work either.
