Posted: Fri Jan 09, 2026 9:30 Post subject: New Build - 01/09/2026 - r63295
Welcome to Atheros r63295 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.
Joined: 05 Oct 2008 Posts: 852 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Fri Jan 09, 2026 9:51 Post subject:
Router XR500
With this build the router cannot resolve hostnames by itself:
Code:
─[✗]─[root@XR500:192.168.5.1]─[~]
└─dig yle.fi
;; UDP setup with ::1#53(::1) for yle.fi failed: address not available.
;; no servers could be reached
;; UDP setup with ::1#53(::1) for yle.fi failed: address not available.
;; no servers could be reached
;; UDP setup with ::1#53(::1) for yle.fi failed: address not available.
;; communications error to 127.0.0.1#53: connection refused
; <<>> DiG 9.20.7 <<>> yle.fi
;; global options: +cmd
;; no servers could be reached
┌─[✗]─[root@XR500:192.168.5.1]─[~]
The last build which could using same settings as they have been for months or longer:
01-01-2026-r63230
LAN has a local DNS server at 192.168.5.62, which is also the local NTP server (localDNS.arnet aka localNTP.arnet).
Judging from its log the local DNS server (PiHole) never gets to see the attempts issued by the router.
Code:
1556 2026-01-01T00:01:36+02:00 xr500.arnet ntpclient[2260]: Connecting to 212.18.3.19 [212.18.3.19] ...
1557 2026-01-09T09:32:35+02:00 xr500.arnet ntpclient[2260]: Time set from 212.18.3.19 [212.18.3.19].
1558 2026-01-09T09:32:35+02:00 xr500.arnet process_monitor[2259]: [ntp] : Cyclic NTP Update success (servers localNTP.arnet 2.poo 1558 l.ntp.org 212.18.3.19 195.171.43.10)
1559 2026-01-09T09:32:35+02:00 xr500.arnet process_monitor[2259]: [ntp] : Local timer delta is 1767951069
NTP update is successful because of the hard coded NTP server addresses.
On build 63230 the first NTP sync would be from localNTP.arnet (has an RTC and battery backup for the server).
Going back to 63230 when other LAN users permit ...
Unless there's a way to solve this problem by changing settings ...
EDIT:
After an hour or so, the router 'stopped working' on build 63295 ... I can't tell what happened.
Tried to go 'down' with easyddup, but the script didn't function/start (like dead).
A router reboot helped enough to be able to download the required file for build 63230, so I downgraded via the GUI. The bin-file would probably have been available on the thumbdrive for easyddup/optware, but there was panick in the air ...
Based on my limited observations I would advise to be weary of upgrading routers that had problems with the chronically previous build. It does not look like they have been solved yet.
EDIT2:
Apologies!
I need to retract what I wrote in the first EDIT.
It turns out there's a problem with my local DNS server. Of course, everything stops working when that stops.
Next move will be to try build 63295 again at some point.
Posted: Fri Jan 09, 2026 15:28 Post subject: WR841ND
Router/Version: TP-Link TL-WR841ND v11
Update method: WebUpgrade
File/Kernel: tl-wr841nd-webflash.bin_r63295 / Linux 3.18.140-d6 #256557 Fri Jan 9 10:28:37 +07 2026 mips
Previous/Reset: r63230 / no
Mode/Status: AP wired and wireless / Up and running for 4:01
Issues/Errors: Nothing significant
If your router's light turns red, don't worry. Internet connection is ok.
Incorrect rate of wlan0 - 800 Mbit/s!
Thank you BS and gurus! _________________ Atheros
Netgear XR500 Nighthawk - DD-WRT 63257
Tp-Link TL-WDR4900 v1.3 - DD-WRT 53133
TP-Link WR1043ND v4 - DD-WRT 51838
TP-Link WR1043ND v2 - Gargoyle OS 1.13.0
TP-Link WR841ND v11 - DD-WRT 63257
Broadcom
Asus RT-AC88U - DD-WRT 63257
Asus RT-AC87U R - DD-WRT 63257
Asus RT-N66U - DD-WRT 63257
Linksys WRT54GL v1.1 - DD-WRT 54517M
Linksys WRT54GL v1.1 - FreshTomato 2023.4_MIPS_K26
Linksys WRT54GL v1.1 - Gargoyle OS 1.6.2
Joined: 07 Jan 2025 Posts: 244 Location: Bethel Park, PA, USA
Posted: Fri Jan 09, 2026 16:44 Post subject:
Router/Version: Linksys MR7350 and Linksys MX4300
File/Kernel: DD-WRT v3.0-r63295 std (01/09/26), Linux 6.6.119-rt29 #4981 SMP Fri Jan 9 09:03:54 +07 2026 aarch64
Previous/Reset: DD-WRT v3.0-r61848 std (06/24/25), no reset
Mode/Status: Gateway (NSS-ECM), Access Point (2.4GHz-HT20 N/G Mixed, 5GHZ-VHT80 AX/AC/N mixed, WPA2/WPA3, 802.11r/v/k, domain:UNITED STATES), IPV6 (DHCP6 w/ prefix delegation)
Issues/Errors:
Up 2 hours on APs.
Updated the MR7350 gateway and could not get an IPv6 address, even with a hard reset and basic configuration. Rolled it back to r61848. On the bright side, SmartDNS and DNSMasq seemed to be working as expected. Syslog from the boot process is attached, maybe it will have some info regarding IPv6.
Updated the two APs (one MX4300 and one MR7350) and both seem to be working correctly. Still have one Echo Dot that won't connect on 5GHz after r61848 but everything else seems to be okay, and that Echo will connect on 2.4GHz.
Joined: 05 Oct 2008 Posts: 852 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Fri Jan 09, 2026 18:37 Post subject:
Tried build 63295 a second time on my XR500 with local DNS server like I've been using for a long time now (same configuration as on a R7800 in a different location).
The fact remains that on build 63295 the XR500 itself cannot resolve domain names at all. Queries made in an SSH session on the XR500 don't get passed to the local DNS server (PiHole). This also inhibits using the local DNS server to set the time, unless of course I enter its IP address in the DD-WRT settings instead of the hostname.
It is not caused by my local DNS server.
The first time I upgraded to this build I had apparently pushed the button on its side that stops the Raspberry Pi after a short while while handling the Raspberry Pi. I hadn't noticed it immediately.
Downgraded again to the last working build 63230.
I hope somebody will soon find the cause of this bug.
Shortcut Forwarding Engine: NSS-ECM
QCA NSS Subsystem: enabled
Local DNS: all zeros
DHCP Type: dhcp server
DHCP Server: enable
Start IP Address: 192.168.3.64
Maximum DHCP Users: 190
Lease Expiration: 1440 min
Static DNS 1, 2 & 3: all zeros
Use dnsmasq for DNS: ticked
DHCP-Authoritative: ticked
Enable Client: enabled
Time Zone: set correctly
Update Interval: 86400
Services services tab
Use NVRAM for Client Lease DB: ticked
Enable dnsmasq: enabled
Query DNS in Strict Order: enabled
Maximum Cached Entries: 1500
Maximum Concurrent Requests: 150
Additional Options:
domain-needed
no-negcache
expand-hosts
no-resolv
bogus-priv
server=149.112.112.112
server=9.9.9.9
server=1.0.0.1
server=/pool.ntp.org/time.google.com/149.112.112.112
server=/pool.ntp.org/time.google.com/1.0.0.1
server=/pool.ntp.org/time.google.com/9.9.9.9
listen-address=127.0.0.1,192.168.3.1
All others are disabled, unticked or blank
Last edited by Abboo on Mon Jan 12, 2026 12:17; edited 2 times in total
Router: DIR-825 rev B1
Firmware: dir825-firmware.bin (v3.0-r63295 std)
Kernel: Linux 3.10.108-d11 #213806 Fri Jan 9 08:12:51 +07 2026 mips
Status: Working
Reset: None
Notes on configuration: Used for Wifi Lab (no internet)
Errors:
Update method: SSH / CLI using PuTTY
Router/Version: Linksys MX8500
File/Kernel: DD-WRT v3.0-r63295 std (01/09/26) / Linux 6.6.119-rt29 #4981 SMP Fri Jan 9 09:03:54 +07 2026 aarch64
Previous/Reset: DD-WRT v3.0-r62966 std (12/06/25) / Linux 6.6.118-rt29 #4715 SMP Sat Dec 6 10:22:51 +07 2025 aarch64
Mode/Status: Gateway / Failed Issues/Errors: No 5GHz Radio
As with all builds since 62966, the 5GHz radio is not functional. I will fall back to 62966.
Same here no 5Ghz but I decided to stay and check, also found out that ports 1 and 4 on the router are not working, went back to previous version I had 62778 _________________ Linksys MX8500
Last edited by blaser on Mon Jan 12, 2026 11:50; edited 1 time in total
Tried build 63295 a second time on my XR500 with local DNS server like I've been using for a long time now (same configuration as on a R7800 in a different location).
The fact remains that on build 63295 the XR500 itself cannot resolve domain names at all. Queries made in an SSH session on the XR500 don't get passed to the local DNS server (PiHole). This also inhibits using the local DNS server to set the time, unless of course I enter its IP address in the DD-WRT settings instead of the hostname.
It is not caused by my local DNS server.
The first time I upgraded to this build I had apparently pushed the button on its side that stops the Raspberry Pi after a short while while handling the Raspberry Pi. I hadn't noticed it immediately.
Downgraded again to the last working build 63230.
I hope somebody will soon find the cause of this bug.
Just to give a hint, FWIW...
On my Netgear R7800, acting as main router, r63295 can resolve names, DNS works.
I has just a normal DNSmasq setup, with 8.8.8.8 and 1.1.1.1 as DNSs.
Computers conected to them can resolve names through 192.168.1.1.
On a R6250 used as Repeater Bridge, and using main router (192.168.1.1) as DNS, it does not work. Reverting repeater to r63230, it can resolve names again.
Joined: 05 Oct 2008 Posts: 852 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Mon Jan 12, 2026 11:14 Post subject:
jamagallon wrote:
On a R6250 used as Repeater Bridge, and using main router (192.168.1.1) as DNS, it does not work. Reverting repeater to r63230, it can resolve names again.
Don't know if this gives a clue...
In my case it's the main router that advertises the DNS server on the local LAN to the clients of the router. The clients can all access this server and DNS works as intended, also on the latest builds (in as far as I have had it running before downgrading again).
The DNS server address is set in Static DNS 1 on the Basic Setup page.
Since the recent upgrade from 63230, however, the router itself lost access to this DNS server, just like your repeater did.
In my imagination(?) the values in the GUI are 'translated' and written into the actual settings used by the router and perhaps this particular value is lost in translation on the more recent builds.
At one time years ago the DNS server to be advertised to the clients was given in additional dnsmasq settings instead of in the Basic Setup page of the GUI and that might be a way around this bug,
I have not yet endeavoured to try and find if anything went missing from the actual dnsmasq settings (to be found in some file on the router), if indeed this is the case.
It is just my guess. It could be something quite different.
I was hoping there are some more experienced users here who know exactly what to look for and what to expect ...
on the more recent builds.