Author
Message
blkt DD-WRT Guru Joined: 20 Jan 2019 Posts: 6381
Posted: Tue Dec 16, 2025 10:17 Post subject: New Build - 12/16/2025 - r63093
Welcome to Marvell r63093 beta release thread for reporting, feedback to developers and community benefit.
Please do not flash builds until installation is understood, risks involved and device specific recovery 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} ' (http only ) or 'curl -O {file URL} ' (http , https , ftp ) 'write {file} linux ' then 'reboot '.
Downloads : HTTPS , FTP
Trac SVN : repository since last build r63020 (mirror )
• Open VPN 2.6.15 : Changelog , Guides, Server, PBR, DNS, Kill Switch, Watchdog, Reverse PBR, Client, Multiple, tips, scripts .
• WireGuard 1.0.20211208 /Tools : Changelog , Guides, Client, Server, Adv, PBR, KS, tips, scripts . Thanks BS egc & eibgrad!
Notes : ...
r61542 r61557 r61613 r61648 r61711 r61745 r61848 r61915 r61920 r61954 r61970 r61981 r62032 r62036 r62104 r62157
r62170 r62192 r62240 r62268 r62324 r62365 r62374 r62418 r62460 r62508 r62540 r62606 r62778 r62890 r62966 r63020
r63093
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: strace tcpdump .
• 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 .
Example Template : Code: [b]Router/Version: [/b]
[b]File/Kernel: [/b]
[b]Previous/Reset: [/b]
[b]Mode/Status: [/b]
[b]Issues/Errors: [/b]
Back to top
Sponsor
Rickers DD-WRT User Joined: 10 May 2015 Posts: 175
Posted: Tue Dec 16, 2025 21:20 Post subject:
Router/Version: 1900ACv1
File/Kernel: 63093
Previous/Reset: 59045/Factory Reset
Mode/Status: AP
Issues/Errors: Client traffic not being routed to internet. This was tested on factory defaults. Back to 59045.
Notes
Can we get this ubootenv issue fixed on 1900ACv1? It's been there a while...or is that unit not supported any more?
"ubootenv list" problem still exists:
Used power switch procedure to manually switch partitions and boot back into 59045 and then reloaded prior settings.
Back to top
marcus83 DD-WRT User Joined: 04 Jan 2024 Posts: 300
Back to top
MBehr DD-WRT User Joined: 27 Nov 2018 Posts: 69
Posted: Wed Dec 17, 2025 4:24 Post subject:
Router/Version: WRT1900ACv2
File/Kernel: DD-WRT v3.0-r63093 std (12/16/25)
Previous/Reset: none
Mode/Status: AP
Issues/Errors: none
Back to top
marcus83 DD-WRT User Joined: 04 Jan 2024 Posts: 300
Posted: Thu Dec 18, 2025 7:24 Post subject:
marcus83 wrote: always the same problem...WRT3200ACM (AP) does not load data:
I'm stuck on the version: DD-WRT v3.0-r62606 std (11/12/25)
does anyone know how to solve this problem?
Back to top
kernel-panic69 DD-WRT Guru Joined: 08 May 2018 Posts: 16703 Location: Texas, USA
Posted: Thu Dec 18, 2025 17:04 Post subject:
It's probably due to the shift to nftables / iptables-nft and not wanting to maintain several versions of the webUI:
Code: iptables -vnL
Chain INPUT (policy ACCEPT 2307 packets, 776K bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 36 packets, 47510 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 2673 packets, 759K bytes)
pkts bytes target prot opt in out source destination
Code: iptables-nft -vnL
# Warning: iptables-legacy tables present, use iptables-legacy to see them
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
23M 19G SECURITY all -- * * 0.0.0.0/0 0.0.0.0/0
23M 19G ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
1361 74075 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID
0 0 ACCEPT udp -- wan * 0.0.0.0/0 0.0.0.0/0 udp spt:67 dpt:68
2353 198K DROP icmp -- wan * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT 2 -- wan * 0.0.0.0/0 0.0.0.0/0
133K 9830K ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 state NEW
171K 8657K ACCEPT all -- br0 * 0.0.0.0/0 0.0.0.0/0 state NEW
0 0 ACCEPT all -- br0 * 0.0.0.0/0 0.0.0.0/0
2035 486K tarpit all -- * * 0.0.0.0/0 0.0.0.0/0
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
50612 31M SECURITY all -- * * 0.0.0.0/0 0.0.0.0/0
49402 31M ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
16 1476 tarpit tcp -- * wan !192.168.0.19 0.0.0.0/0 state INVALID
1194 307K upnp all -- * * 0.0.0.0/0 0.0.0.0/0
1194 307K lan2wan all -- * * 0.0.0.0/0 0.0.0.0/0
0 0 REJECT tcp -- br0 wan 0.0.0.0/0 0.0.0.0/0 WEBSTR match content 3 reject-with tcp-reset
0 0 ACCEPT all -- br0 br0 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT tcp -- * wan 192.168.1.0/24 0.0.0.0/0 tcp dpt:1723
0 0 ACCEPT 47 -- * wan 192.168.1.0/24 0.0.0.0/0
0 0 ACCEPT udp -- wan * 0.0.0.0/0 224.0.0.0/4
0 0 TRIGGER all -- wan br0 0.0.0.0/0 0.0.0.0/0 TRIGGER type:in match:0 relate:0
1194 307K trigger_out all -- br0 * 0.0.0.0/0 0.0.0.0/0
0 0 TRIGGER all -- wan lan1 0.0.0.0/0 0.0.0.0/0 TRIGGER type:in match:0 relate:0
0 0 trigger_out all -- lan1 * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT all -- lan1 * 0.0.0.0/0 0.0.0.0/0 state NEW
0 0 TRIGGER all -- wan lan2 0.0.0.0/0 0.0.0.0/0 TRIGGER type:in match:0 relate:0
0 0 trigger_out all -- lan2 * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT all -- lan2 * 0.0.0.0/0 0.0.0.0/0 state NEW
0 0 TRIGGER all -- wan lan3 0.0.0.0/0 0.0.0.0/0 TRIGGER type:in match:0 relate:0
0 0 trigger_out all -- lan3 * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT all -- lan3 * 0.0.0.0/0 0.0.0.0/0 state NEW
0 0 TRIGGER all -- wan lan4 0.0.0.0/0 0.0.0.0/0 TRIGGER type:in match:0 relate:0
0 0 trigger_out all -- lan4 * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT all -- lan4 * 0.0.0.0/0 0.0.0.0/0 state NEW
0 0 TRIGGER all -- wan wlan0 0.0.0.0/0 0.0.0.0/0 TRIGGER type:in match:0 relate:0
0 0 trigger_out all -- wlan0 * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT all -- wlan0 * 0.0.0.0/0 0.0.0.0/0 state NEW
0 0 TRIGGER all -- wan wlan1 0.0.0.0/0 0.0.0.0/0 TRIGGER type:in match:0 relate:0
0 0 trigger_out all -- wlan1 * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT all -- wlan1 * 0.0.0.0/0 0.0.0.0/0 state NEW
1194 307K ACCEPT all -- br0 * 0.0.0.0/0 0.0.0.0/0 state NEW
0 0 ACCEPT all -- br0 wan 0.0.0.0/0 0.0.0.0/0
0 0 tarpit all -- * * 0.0.0.0/0 0.0.0.0/0
Chain OUTPUT (policy ACCEPT 11M packets, 1878M bytes)
pkts bytes target prot opt in out source destination
9288K 17G ACCEPT all -- * br0 0.0.0.0/0 0.0.0.0/0
Chain SECURITY (2 references)
pkts bytes target prot opt in out source destination
Chain advgrp_1 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_10 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_11 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_12 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_13 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_14 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_15 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_16 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_17 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_18 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_19 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_2 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_20 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_3 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_4 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_5 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_6 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_7 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_8 (0 references)
pkts bytes target prot opt in out source destination
Chain advgrp_9 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_1 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_10 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_11 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_12 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_13 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_14 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_15 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_16 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_17 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_18 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_19 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_2 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_20 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_3 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_4 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_5 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_6 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_7 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_8 (0 references)
pkts bytes target prot opt in out source destination
Chain grp_9 (0 references)
pkts bytes target prot opt in out source destination
Chain lan2wan (1 references)
pkts bytes target prot opt in out source destination
Chain portscan (0 references)
pkts bytes target prot opt in out source destination
0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 0 level 4 prefix "portscan:"
0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0
Chain tarpit (3 references)
pkts bytes target prot opt in out source destination
2051 487K DROP all -- * * 0.0.0.0/0 0.0.0.0/0
Chain trigger_out (7 references)
pkts bytes target prot opt in out source destination
Chain upnp (1 references)
pkts bytes target prot opt in out source destination
Code: iptables-legacy -vnL
Chain INPUT (policy ACCEPT 3455 packets, 1096K bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 36 packets, 47510 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 3846 packets, 1069K bytes)
pkts bytes target prot opt in out source destination
In other words, you're probably not going to be able to track by device unless you use some kind of magic voodoo via CLI. I didn't go that far into it.
_________________"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
Back to top
dd4st DD-WRT Novice Joined: 13 May 2024 Posts: 2
Posted: Fri Dec 19, 2025 1:17 Post subject: PTY allocation / fopen mtdblock failed
This appears to be the same issue as reported for r62966 .
Attempting to upgrade from v3.0-r57595 std fails. Had to do the 3x power reset to return to previous boot partition.
Symptoms:
1) WiFi and WAN fail but Ethernet connections work
2) SSH fails with:
```
PTY allocation request failed on channel 0
shell request failed on channel 0
```
3)Attempt to execute _any_ command results in:
```
fopen('/dev/mtdblock/1','r') fail. [No such file or directory]
```
Back to top
kernel-panic69 DD-WRT Guru Joined: 08 May 2018 Posts: 16703 Location: Texas, USA
Back to top
dd4st DD-WRT Novice Joined: 13 May 2024 Posts: 2
Posted: Fri Dec 19, 2025 18:58 Post subject:
That's correct. I apologize for the brief post. Some issues and time constraints on my end and I rushed it out.
A bit more detail:
Board: Linksys WRT1900AC v1
Upgrading from v3.0-r57595 std.
Problem occurs when upgrading to v3.0-r62966 or v3.0-r63093
Back to top