Hey @hecatae how are you getting on with the stable release of openwrt 24.10? Working ok for me apart from I can no longer successfully run controld via ssh. The binary installs but isn’t working. Looks like their DNS isn’t pushing out to any clients via my Orbi RBK50 mesh system as per normal and controld status is “not using controld”. Looks like something weird is going on with vanilla openwrt vs glinet version. Maybe a name resolution issue somewhere. Really weird!
I’ve ran dnsmasq and got lots of strange entries “no default route present”.
Install owut using opkg install owut, then run owut check to see if there's any new packages.
owut download and owut install to install.
Openwrt buildbots have been rerun as some targets were incomplete.
Thanks @hecatae
Weird
owut - OpenWrt Upgrade Tool 2025.01.29~bced54ad-r1 (/usr/bin/owut)
ERROR: Failed to connect
ERROR: Response status (null) while downloading
https://sysupgrade.openwrt.org/json/v1/overview.json
@hecatae I got Controld working via installing adguard bit not a fan of that. Got owut working after removing adguard.
wut - OpenWrt Upgrade Tool 2025.01.29~bced54ad-r1 (/usr/bin/owut)
ASU-Server https://sysupgrade.openwrt.org
Upstream https://downloads.openwrt.org
Target mediatek/filogic
Profile glinet_gl-mt2500
Package-arch aarch64_cortex-a53
Root-FS-type squashfs
Sys-type sysupgrade
Version-from 24.10.0 r28427-6df0e3d02a (kernel 6.6.73)
Version-to 24.10.0 r28427-6df0e3d02a (kernel 6.6.73)
Build-FS-type squashfs
Build-at 2025-02-03T23:09:37Z (~113 hours ago)
Image-prefix openwrt-24.10.0-mediatek-filogic-glinet_gl-mt2500
Image-URL https://downloads.openwrt.org/releases/24.10.0/targets/mediatek/filog
Image-file openwrt-24.10.0-mediatek-filogic-glinet_gl-mt2500-squashfs-sysupgrade.b
Installed 175 packages
Top-level 92 packages
Default 35 packages
User-installed 63 packages (top-level only)
Package version changes:
All packages are up-to-date
Default package analysis:
Default Provided-by
nftables nftables-json
There are currently package build failures for 24.10.0 aarch64_cortex-a53:
Feed: telephony
freetdm Fri Feb 7 18:37:50 2025 - not install
Failures don't affect this device, details at
Index of /releases/faillogs-24.10/aarch64_cortex-a53/
There are no changes, upgrade not necessary
So I’ll have to wait for a new build that hopefully fixes this!
1 Like
I tried running the Control D install script on 24.10 RC7 on the Flint 2 and had the exact same issue.
Contacted Control D and sent them the logs. This is what they replied with;
Hey,
The error suggests that the ctrld process is attempting to interface with dnsmasq but cannot find the expected ctrld.conf file. This might indicate a configuration issue or that the required directory/file is missing. Please ensure that dnsmasq is installed and running, and that the /tmp/dnsmasq.d/ path exists.
For the warning about "no default route IP found", this might indicate that the networking setup might not have a default route configured, which ctrld expects. Ensure your network interface is up and has a connection to your gateway.
Could you confirm that dnsmasq is configured and running? Additionally, can you check your network interface settings to ensure it's properly configured?
The OpenWRT logs suggest that the network interface might not have been assigned a default gateway IP. You may need to ensure that your network interface configuration on OpenWRT is correct and has a proper gateway set up.
Ensure that dnsmasq and ctrld permissions allow them to create and access necessary files, and check the network route configuration on your OpenWRT device. Try restarting both services after confirming these settings.
Let us know how that goes.
I ran out of time to mess around with it, flashed stock GL-iNet back on it for now. The Control D script installs correctly on stock firmware. I was also running a custom build by Pesa and the script worked fine on there too. It is some sort of change on the 24.10 that is not allowing it to install and run correctly.
Hi
I contacted controld and as well. They said they were going to try their binary with the latest 24.10 openwrt release and test. Whether they will or not is another matter. But after cycling through the openwrt forums there are quite a few similar issues reported re dns proxy’s not working across the board since the 24.10 line started. So I don’t believe this is a coincidence. And these are across a variety of different hardware configurations/models. There is clearly a major compatibility issue with the 24.10 branch and dns proxy setups. This needs to be addressed by openwrt.
Something also weird with 24.10, my work vpn using windows l2tp client doesn’t work either. No issues with this or controld on gl.iNet firmware.