OpenWrt 24.10.0-rc4 - Fourth release candidate

This will sadly not work, The ctrld cli has been broken in 24.xx.xx and we've had to use workarounds to get it to work, add the below lines to your backup configuration file to ensure the cli survives upgrades and change this line in the /etc/init.d/dnsmasq file. config_get dnsmasqconfdir "$cfg" confdir "/tmp/dnsmasq${cfg:+.$cfg}.d" to: config_get dnsmasqconfdir "$cfg" confdir "/tmp/dnsmasq.d" , the cause is because dnsmasq now creates a unique dir for each instance rather than the old /tmp/dnsmasq.d and I've seen reports from other apps affected by this issue, I got the above from Ctrld's github issues page not sure if I am allowed to post here, but there are similar posts on the openwrt github pages from devs whose apps are affected by these changes.

/usr/sbin/ctrld
/etc/init.d/ctrld
/etc/controld/ctrld.toml
/etc/init.d/dnsmasq

PS, just upgraded to RC5 and my ctrld cli is still working.

I'm not sure we are talking about the same issue here. You are talking about the ControlD CLI not working due to changes to how dnsmasq operates in 24.10.x. I am talking about using the https-dns-proxy (plus Luci GUI if you prefer) as a way to setup ControlD without using ControlD's package or CLI interface. This does not meet @viniribeirossa 's need, because currently, out of the box, https-dns-proxy does not support DOQ/DoH3 without some modification.

Here I have it setup and it works (both in stable and RC versions):

I would suggest that since this is ControlD's package and they sell the service that the issue is perhaps best resolved by them. You are right, I don't know whether the issue is worth/allowed to be mentioned here.

I noticed that after I responded, but the proxy will work for some and not for others since you lose functionality which the cli provides, like assigning different profiles, kids, IoT,etc. to different subnets in ControlD which is not possible when you use the proxy. here is a link about the issue dnsmasq: fix path to default dnsmasq confdir by stangri · Pull Request #16806 · openwrt/openwrt · GitHub

qq, I unknowingly used 24.10.0-rc4 on raspberry pi 4, finished configuration and actively started using it.
If/when a new rc/stable is released, will I be able to safely flash it using System->Flash Firmware by persisting my configs?

Yes but keep in mind that user installed packages will not be in the image. Use a tool like auc/owut or attended sysupgrade for an image that contains user installed packages.

2 Likes

Does that mean I go https://firmware-selector.openwrt.org/?version=24.10.0-rc5&target=bcm27xx%2Fbcm2711&id=rpi-4 expand Customize installed packages and/or first boot script and mention jq curl (assuming those two are my user installed packages) and click Request Build. Once done, download that package and flash via System->Flash Firmware ?

Also any easy to way to list all packages I installed?

That is manually using the firmware selector. Think of attended sysupgrade and auc/out as tools to automate a custom build.

Any wiki document I can read about it?

First hit on Google: https://openwrt.org/docs/guide-user/installation/attended.sysupgrade

This does not mention owut but out is going to replace auc. Documentation over here: https://openwrt.org/docs/guide-user/installation/sysupgrade.owut

3 Likes

FriendlyARM NanoPi R4S 1GB not bootable,is the official plan not to support ?

Not sure if this is similar to your situation, but someone with an RP4 upgrading to 24.10-rc4 indicated issues when using owut with the option to resize the rootfs.
https://forum.openwrt.org/t/owut-openwrt-upgrade-tool/200035/368

Was the 1gig version ever supported? I didn't think it was though could be wrong...
The ToH says 1GB version - currently the 1GB RAM version is not bootable from snapshot. For this use one of the unofficial builds linked below:

See https://openwrt.org/toh/friendlyarm/nanopi_r4s_v1

I know, so I would like to ask if the official does not plan to continue supporting the 1G version.I am currently using immortalwrt

does this issue fixed in 24.10 rc5?

24.10.0-rc5 didn't bring up my Filogic 5ghz radio so tread carefully.

Edit: Reset my config and now its working.

2 Likes

I would not install RC5 until it is announced. The build bots have finished the builds, but Hauke hasn't announced it yet. There could still be issues that needs resolving. I remember RC4 being built shortly after RC3 because of such an issue. The dangers are made clear here by NDB.

10 Likes

Absolutely, I'm just saying heed that advice extra closely, it's no big deal for me to rollback but if you're feeling impatient, definitely wait a bit on this one.

OpenWrt 24.10.0-rc5 was announced, see OpenWrt 24.10.0-rc5 - Fifth release candidate

Closing this thread now.

7 Likes