Posted: Sat Jan 17, 2026 15:01 Post subject: New Build - 01/17/2026 - r63391
Welcome to Marvell r63391 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.
Wired clients can be made to work:
1. Disable Shortcut Forwarding Engine (SFE).
2. Set DNS to 8.8.8.8
3. Uncheck 'Use dnsmasq for DNS'. dnsmasq keeps crashing on startup so disable it.
4. Check 'Recursive DNS Resolving (Unbound)'. Appears to be necessary for this work-around.
Reboot and wired clients will work, at a reduced throughput for me. Works, but not really usable.
It's possible to SSH in:
Enable SSH.
"ssh root@192.168.1.1" gives an error "PTY allocation request failed on channel 0 shell request failed on channel 0".
I googled the error and found a solution: "ssh root@192.168.1.1 /bin/sh -i" will let you get a command prompt. Note that the term isn't set up properly so things like vi don't work right.
However, you can poke around. The most obvious problem is that the /dev directory is missing a lot of items, most notably, the 'mtd' and 'mtdblock' directories which cause the boot environment to be unavailable.
Last edited by Rickers on Mon Jan 19, 2026 7:37; edited 1 time in total
Router: Linksys WRT1900ACSv2
Firmware: DD-WRT v3.0-r63390 std (01/17/26) from r58389.
Kernel: Linux 6.1.161-rc1-rt28 #323 SMP Sat Jan 17 13:07:51 +07 2026 armv7l
Reset: No.
Mode/Status: Ignore WAN DNS; SFE Disable; Use Dnsmasq & SmartDNS Resolve.
Wi-Fi: wlan0 - AP,AC/N-Mix,VHT80; wlan1 - AP,N-Only,HT40.
USB Storage Support via USB 3.0: --- /dev/sda - Block device, size 3.639 TiB, Ext4, with two partitions: one mounted in /jffs, the second in /opt.
NAS: Samba Protocol 2.10\3.11; NFS Server - Enable;
Issues/Errors: Haven't noticed yet.
Please note that the router shows firmware r63390 but not r63391.
I noticed that the firmware no longer contains /opt/bin/udpxy. _________________ Linksys WRT1900ACSv2
Automatically adjustable temperature, always within the range of 48-53°С.