I am facing an issue where I cannot create backup of my config using either lucy or CLI. With luci, it hangs while generating the backup so I save a file with zero bytes after waiting like forever.
On the CLI, it also hangs:
``
root@DL-WRX36:~# umask go=
root@DL-WRX36:~# sysupgrade -b /tmp/backup-${HOSTNAME}-$(date +%F).tar.gz
Wed Oct 8 18:46:23 EAT 2025 upgrade: Saving config files...
``
This started only this week.
I am running 24.10.2 lastly compiled today from firmware-selector.openwrt.org.
So a couple of years ago, when the community was working on hacking this router to be able to flash it, I tried some things with the stock firmware first. Though unsuccessful, I did find a bug that downloaded what I thought were junk files by changing the version URL from 0.10.01 to 1.10.01, and then clicking or typing in various links (such as /cgi/SaveSysLog.cgi).
I ran across these files earlier tonight while clearing out old files in my projects archive and decided to examine them. They were 1.7 MB in size eah.
The CGI files that downloaded was actually a 1.7 MB ELF Binary. Iāve come to the supposition that the files were actually dumps of the running binary (running the webui). I ran it through a couple of AIās and theyāve come about the same point.
There are numerous samples of the files from back in Dec. 2022 in the Google Drive link below. Also included:
- OEM Image for version 1.10.01.201
- The settings file that can be uploaded to enable the SSH server.
- A file of some of the functions cleaned up from binary data, including what I feel is the most important (adminrm.c), but Iāll get to that in the a moment.
The reason Iām sharing this is to seek guidance, because there are a couple of undocumented āfeaturesā in the OEM firmware that people might want to know about. Whether itās because Askey provided an overall master-image and just dummied-out some functionality, or if itās potentially actively malicious (monitoring, considering how cheap this hardware was on releaseā¦.), Iām not sure. But here are three undocumented bits:
- OneAgent TR-069-This is not mentioned anywhere in documentation, but appears to be a installed, yet hidden remote management system. OneAgent is a ISP-Grade TR-069 Remote Management Tool. I found references in the ācgiā copies of the Webui server binary:
File Path: function/adminrm.c
Service Restarts: The binary contains the literal commands to restart the agent, including/etc/init.d/tr_oneagent_proxy restart
/etc/init.d/oneagent_mon restart
/etc/init.d/tr-069 restart
Service Components: It explicitly references the OneAgent bootstrap flag/oneagent/conf/.FLAG_BOOTSTRAP
Username/Password: Looks like if TR-069 OneAgent is activated, it has hardcoded user/pass:/oneagent/conf/.FLAG_BOOTSTRAP UserName_ASKEY UserName_ASKEY1 ASKEY1 Askey1Pwd - File Path: function/netprinter.c
I found no references anywhere in the documentation to a printer. It appears to linked against libcups.so.2, and uses cupGetDevices, ippNewRequest and cupsDoFileRequest.
There also appears to be samba. print[0].printer. - WebDAV exists in the firmware but not the documentation. WebDAV http[s] ports: 8081/8844 are defined in global[0]. WebDAV can also be seen in the js files, but is not built in as a feature per the documentation. I remember when I was playing with the WebUI, I was able to re-enable WebDAV fairly easily.
- Other oddities:
- Ports 6665 6666 6667 6668 6669 are reserved in global[0] context..
- @global[0].user_out_http_port is defined as 8080 / 8443ā built in ports for WAN side access, maybe through the app?
- @global[0].http_port is set to 80/443, though the router doesnāt have a way to assign usable certificates.
- [Edit: Forgot this one] I found that there was another subnet besides the OEM (which was in 192.168.216.0/24)ā I cannot remember the exact one, but it was something like 192.168.17.0/24. The random user/password, nor the password set upon setup worked in this subnet. I half wonder if itād work using
āAskey1Pwd" or "Askey123"?
Needless to say, Iām really happy I installed the real OpenWRT on this router.
My question though is how to proceed? I donāt want to reflash this cruddy firmware for testing if the newest version still has these issues.
Either way, wanted to warn the OEM users that thereās potentially shady stuff in this router.
[PLEASE NOTE: Not sure if the newer OEM versions have this same issue, this data was from back in December 2022]
[EDITS:
Edit 1: Fixed two typos,
Edit 2: Corrected the UCI references using the at sign before global[0] and print[0]ā they were omitted because after posting, formatting changed.
Also added the noted section above about the extra subnet.]
Latest 24.10.4 includes the fix in Linux kernel 6.6.105, I can hit 700 Mbps over Wifi 6 (ac), no error or hangup yet since flash.
24.10.4 does include the fix, but it gets the fix via the mac80211 update from 6.12.44 to 6.12.52, even though the rest of the kernel is 6.6.110. Mind-bendingā¦ 
So I use my Dynalink WRX-36 as an intermediate BATMAN node that uses wireless (802.11s) + wired backhaul. My environment has mixed devices.
I just found out today that in order to extract better performance (observed in some of the hops) I had to set frame_mode=0 in ath11k. This seems to happen as BATMAN encapsulation over Ethernet is >1500, and I guess the firmware assistance has trouble on ethernet+wireless concurrently.
Iāve added it to my use case via:
root@WRX36:~# cat /etc/modules.conf
# examples:
# options mod1 option=val
# blacklist mod2
options ath11k frame_mode=0 ftm_mode=N
For me this makes my BATMAN mesh network more predictable and finally was able to get down to sub 0.1% packet loss according to Orb sensors.
so with the ath11k multicast fixes, and the fix (presumably manual build ? ) to remove the packet flushing , is this now super stable ? I am wondering about coming back to it
I have the same question: whatās the current support status for this device? Is it stable? No freezes, restarts, strange performance degradation, dropout events?
Iāve been running the same frankensetup for these past 2.5 years, where my elderly TL-WR1043NDv1 acts as the primary firewall+gateway and 2.4 GHz provider, with the DL (still at the initial stock v1.10.01.222) patched in to provide 5 GHz on a secondary subnet.
Since the stock QSDK derivative, based on the severely outdated, downright antique Chaos Calmer, is functionally crippled (as stock firmwares tend to be), even though this setup seems to be safe and stable, it limits my 1G optics connection to the ~560 Mbps, and the configuration options to those of v22.03.7 on 8M flash with 32M RAM, that the TL can handle, so I would very much like to finally be able to fully migrate to the DL and unlock its full potential with the latest stable OWRT firmware.
@frollic, @hnyman, @rmandrad, @sampson, @egc, @sqrwv, @greem and anyone else with the device, whatās your experience, is it time to flash?
The router is nowadays quite stable. The early WiFi stability troubles have disappeared.
I am using it as a dumb AP running up-to-date main/master snapshot builds.
I'm also using two as APs, uptime is as long as the last power outage, in my case currently around 200 days.
It is working stable for me but it is lightly used but it has a lot of packages installed, it runs as a test-bed in my home lab.
I am running snapshot for my routers. Wifi speed is good - iPhone 15 got 850Mbps with fast.com, while upload > 512Mbps.
I use it as my router, with https-dns-proxy, adblock and banip.
Recently went from snapshot to 25.12.2, both are stable for me.
I recomend the upgrade, it has a lot of CPU and RAM.
I've got two in long term service, one as my border router attached to a full fibre 1Gbps connection, and the other as an access point with 802.11s mesh networking out to a pair of Zyxel WSM20 APs.
It's running Adblock, DOH proxy, Tailscale and a couple of other things with both physical and dot1q vlan interfaces.
It's been rock solid for a year or more.