OpenWrt 25.12.0-rc4 - Release Candidate

Not exactly what i typed..... Try to enclose the command in ticks 2ticks parentheses etc, whatever is consumable to sh -c should work here....

I tried both of the following approaches in LuCI, and neither of them worked. Could this be a bug?

42 5 * * * /bin/sh -c "sleep 70 && touch /etc/banner && /sbin/reboot"

And the more explicit version:

42 5 * * * /bin/sh -c "/bin/sleep 70; /bin/touch /etc/banner; /sbin/reboot"

In both cases, the cron job did not run and the router did not reboot.

You tried none of approaches
1 1 1 1 1 "sleep 70 ; reboot"
1 1 1 1 1 (sleep 70 ; reboot)

1 Like

I sincerely apologize — the issue was entirely my mistake.

I was testing the rc4 build and did not restore my backup because many things were not working, so I have been configuring everything manually. I ended up forgetting to set the correct UTC/timezone for my region (state).

I fixed that now, and the cron job is working correctly:

24 6 * * * sleep 70 && touch /etc/banner && reboot

Once again, I’m sorry for taking your time with this and thank you for your help.

4 Likes

Adblock Fast appears to work now after the Luci & Adblock Fast upgrades. Thank you.

Extra: Also Windows is back to normal in logging in to WiFi.

root@JG924A:~# ubus call system board
{
        "kernel": "6.6.119",
        "hostname": "JG924A",
        "system": "RTL8382",
        "model": "HPE 1920-24G (JG924A)",
        "board_name": "hpe,1920-24g",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.5",
                "revision": "r29087-d9c5716d1d",
                "target": "realtek/rtl838x",
                "description": "OpenWrt 24.10.5 r29087-d9c5716d1d",
                "builddate": "1766005702"
        }
}
root@JG924A:~#

I updated JG924A from 24.10.5 to 25.12-rc4 and with the default configuration on both version, the test speeds are different.
This is for 24.10.5:

And this is for 25.12-rc4:

Anyone can confirm that problem??

Not aware of any regressions with that hardware but did you try the usual performance settings are enabled, software flow offloading and packet steering?

Sounds like this: Support for RTL838x based managed switches - #4071 by janh

3 Likes

@phinn, No, I used the default settings for both versions.
@efahl , Yes that sound like my problem.
I've flashed SNAPSHOT r32986-a7756346c7
And now the speed is like on 24.10.5

3 Likes

how certain are we of tickless being present on 25.12?

I can see the commit was indeed pulled to x86’s config-6.6, but the current config-6.12 doesn’t seem to have it… not sure how intentional this is; blame doesn’t make it look deliberate.

Following up on my earlier post, my issue has been resolved. This issue itself was intermittent and could occasionally be fixed by restarting wpad. Seeing this bug report, I looked at the output of brctl show in both 24.10.5 and 25.12-rc4. Notice it creates a new bridge name in 25.12.

24.10.5 with wpad-mbedtls

root@RT3200-AP:~# brctl show
bridge name	   bridge id		    STP enabled	    interfaces
br-lan		   7fff.redacted?	    no		        lan4
            	  				                    lan2
			            				            wan
			                            			wl1-ap0-guest
			                            			lan3
			                            			lan1
			                            			wl1-ap0

25.12-rc4 with wpad-mbedtls

root@RT3200-AP:~# brctl show
bridge name	    bridge id		    STP enabled	    interfaces
brvlan11		8000.000000000000	no
br-lan		    7fff.redacted?	    no		        lan4
							                        lan2
							                        wan
							                        wl1-ap0-guest
							                        lan3
							                        lan1
							                        wl1-ap0

I ended up replacing wpad-mbedtls with wpad-basic-mbedtls in 25.12 and it’s working consistently after several reboots over the last couple of days. I checked the output of brctl show and noticed it was now identical to the output I was seeing from 24.10.5 with wpad-mbedtls.

In the end I’m happy. I’m now able to use the well tested default package.

On the router things have been great. The only minor issue I had was needing to update /etc/profile to take advantage of the new .hush option.

Thanks team for all your hard work!!

2 Likes

Config files do change between kernels, but yea I see no_hz=y, no_hz_full and rcu_lazy are removed, and also no_hz_periodic=y. So no clue what’s going on in 25.12. But like I said I’m not using x64 anymore just the mt6000 so I can’t test.

Has there been any changes to when DHCP is used on the WAN interface?

My ISP gives me a 1 hour lease, and I know usually leases renew halfway through their lease, but on 25.12 this seems to renew right at lease expiration suddenly. Is this expected now?

I transitioned to this RC and I have one problem with it.
I have been using the following packages:
luci-app-statistics collectd-mod-thermal collectd-mod-processes collectd-mod-ethstat collectd-mod-ipstatistics collectd-mod-ping luci-mod-rpc collectd-mod-cpu collectd-mod-cpufreq collectd-mod-df collectd-mod-dns

What happens with the 25.12-RC series is that the statistics would load for some time then completely stop registering any data.

I replace my Asus Router with an Intel N150 firewall appliance bought from Aliexpress and run proxmox 9 on it, create a VM OpenWRT x86 and use it as my main internet router, and it has been superb for weeks on end no issues, never have to reboot, old Asus has to reboot every week .. I have other LCX and VM run on same Promox for adblock, IDS, home assistance etc... bloody amazing stuff

And if I ever need to reboot it takes 15 seconds to come back, old Asus took close to 5 minutes, can't go back to one of the vendor router anymore... I keep buying these appliances and build everything myself

2 Likes

oh well my virtualized owrt was perfect in 22, 23 and is perfect in 24, honestly happy to know it’s getting better but i’m not sure i’ll notice :smiley:

(vm under N100 proxmox. for years. no way to go back)

No Idea I start off with 25 just prior RC1 had no issue with it it been awesome :slight_smile: never go back to old ways

i was replying to @RHBH :slight_smile:

I have noticed in the past that luci-app-statistics tends to do that if a collector is configured but not installed. Can usually see in the logs an error related to which one is missing when the service starts.

Less of an issue with tools like owut and attended sysupgrade that can build a new firmware image that includes the currently installed packages making it less likely to miss installing one.

1 Like

Thank you for that. Let me check if I configured something that I did not install during the move to the RC.