Posted: Fri Dec 19, 2025 16:31 Post subject: New Build - 12/19/2025 - r63123
Welcome to Marvell r63123 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.
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.
Possible problems on the latest version de dd wrt, router wrt1900acs v2, the processor is full loud without having traffic on the router or running something that would keep it busy, IPv6 doesn't seem to be working, I restarted the router and it still behaves the same way.
problems on the latest version de dd wrt, router wrt1900acs v2, the processor is full loud without having traffic on the router or running something that would keep it busy it manifests itself again, very strange because I removed all the cables from the router, even the one coming from the ONT and I connected to the router via wifi and it still remained 100% an after reboot it now stays at 50%
The 100% sirq error means that the network driver is trying to process a hardware interrupt that never completes. Either the SFE module is missing, but the system is trying to call it. or the new kernel in r63123 has a conflict with the Marvell driver for managing network queues
How would you know that the system is trying to load the SFE module ... logs? Is console_debug=1 enabled via nvram set? A whole lot of assumptions without anything other than screenshots, and we already know SFE is fairly broken in more recent releases, so enabling it is moot.
I solved it by downgrading, now the performance is optimal with Firmware: DD-WRT v3.0-r62606 std (11/12/25) _________________ Internet provider https://en.wikipedia.org/wiki/RCS_%26_RDS 1Gbps
WDR3600 rev.1.5 - DD-Wrt
Linksys WRT1900ACS v.2 DD-Wrt/-OpenWrt
GL-MT6000 OpenWrt