Posted: Mon Dec 01, 2025 13:00 Post subject: New Build - 12/01/2025 - r62890
Welcome to Atheros r62890 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 Model: TP-Link TL-WR841ND v11
Firmware Version: DD-WRT v3.0-r62890 std (12/01/25)
Kernel Version: Linux 3.18.140-d6 #252883 Mon Dec 1 07:55:44 +07 2025 mips
Previous/Reset: Update via CLI from r62540 / Reset = Yes
Mode/Status: Working OK as AP, NG-Mixed, Wide 40
Issues/Errors: None so far
Many thanks BS! _________________ Router:TP-Link TL-WR841ND v11
Router/Version: Netgerar r7800
Previous/Reset: no
Mode/Status: AP
Issues/Errors: i have two virtual interfaces (2.4 and 5 ghz) bridged on subnet as quest network. Neither iptables nor nftables work for me on this build either.
Posted: Mon Dec 01, 2025 21:42 Post subject: Linksys MR7350
Update method: WebUpgrade
Router/Version: Linksys MR7350
File: 62890
Previous/Reset: 62606 / no
Mode/Status: Gateway / ok
Issues/Errors: If you are seeing this post, all is ok
Thank you again BS and friends.
�\0
Usually nftables (or a translation layer in it) understands iptables syntax and just translates it to its own.
Router/Version: Dynalink DL-WRX36
File: dd-wrt-webupgrade.bin
Firmware: DD-WRT v3.0-r62890 std (12/01/25) (prev. DD-WRT v3.0-r62778 std (11/21/25))
Kernel: Linux 6.6.118-rc1-rt29 #4650 SMP Mon Dec 1 05:45:39 +07 2025 aarch64
Mode: Gateway, SFE disabled, 2.4G (20MHz mixed, WPA2 Personal, WPA3 Personal / SAE - CCMP-128 (AES)) and 5G (80MHz AX / AC / N Mixed, WPA3 Personal / SAE - CCMP-128 (AES)) wifi, bridged VAP on 2.4GHz, Wireguard for external access, WAN disabled, Keep Alive reboot 6:02 in the morning, using my own local NTP
Reset: No
Status: At first wireless wasn't working, even after multiple reboots no 2.4 or 5GHz WLAN. Clicked "Save & Apply" on wireless page and everything started working. Also surviving reboot.
1) Wireless --> Domain set to Germany results in TX Power capped at 14 dBm (2.4GHz) and 18 dBm (5GHz) instead of 20 dBm.
--> Switched Domain to Panama, 20dBm used in both bands.
2) Some MAC Address aren't right. LAN1-4 are correct others are generic 00:00:00:00:00:05, 6, 7 and so on.
--> "nvram erase && reboot" does not fix this. Also unsetting them with nvram unset, commiting and rebooting.
3) 160MHz channel width is offered on 5GHz, but selecting it does result in no wireless being transmitted at all. Even 2.4GHz ceases to work then and status page shows "unknown" on many values then.
Waited several minutes (for shared channels with flight/weather services) but did not come up on lower channels or upper channels.
Joined: 05 Oct 2008 Posts: 850 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Tue Dec 02, 2025 12:30 Post subject:
Zyxx wrote:
Usually nftables (or a translation layer in it) understands iptables syntax and just translates it to its own.
The key word here being 'usually'.
1. I tried 'automatic' translation w/o touching the script -> broke the firewall.
2. I also saved the iptables profile, I think it was called profile, in a router terminal session and then translate the saved profile with a special nftables translation command -> it crashed at something I can find in the saved profile, but don't recognize as originating from a particular iptables rule in my DD-WRT command script.
ChatGPT is not something I am familiar with. AFAIK, its outcome may or may just as well not be correct. I would expect the nftables translation functionality to work better, but apparently it cannot handle all iptables rules. The only rules in my command script that I would call more exotic are like this:
iptables -I FORWARD -p tcp --match multiport --dports 853,5353 -j REJECT --reject-with tcp-reset
iptables -I FORWARD -p udp --match multiport --dports 853,5353 -j REJECT --reject-with icmp-port-unreachable
The above rules are not the rules, however, that the behind the screens translation functionality apparently broke. It was rather the access from some administrator servers on the main LAN to a subnet $VLAN30 with 4 servers by rules, which look quite basic to me:
That being suddenly broken is how I found out there was a move to nftables ...
IIRR, there was an earlier attempt quite some time ago to move to nftables on DD-WRT, but either it was unsuccessful or it didn't concern the R7800 and XR500, which saved me from a headache at the time.
(not being a iptables wizard ... )
Should I just copy the old iptables rules one by one from the command script and somehow feed them to the nftables translation program separately and see how that goes? (i.e. not use the intermediate step of saving the iptables profile? The profile logically contains all rules set up elsewhere in the DD-WRT code, too, so that attempt was probably doomed anyway. Maybe not the way to go forward, but the translation did fail.