Probably should be removed from those places too...
BTW, why logread is littered with that now? Posts every minute. Those jobs are fine and are invoked in their proper times (once a day).
cron.err: crond[3015]: wakeup dt=60
cron.err: crond[3015]: file root:
cron.err: crond[3015]: line /etc/init.d/adblock reload
cron.err: crond[3015]: line /etc/init.d/banip reload
1 Like
Check the “Cron Log Level”.
Ha... you're right. It's "Debug" now. Probably makes sense to pre-releases. Thank you.
From snapshot to 25.12.0-rc1 on two of my Linksys mx5500. And on three Linksys mx5300 from stable (25.10.5) to 25.12.0-rc1, used owut for a change. worked without any problems.
From 24.10.4 to 25.12.0-rc1 on my Nanopi R5S. used owut. worked without any problems.
Thank you to the developers and Merry Christmas to all.
Upgraded yesterday Opwnwrt One with owut from 24.10.4. Merry Xmas to each and everyone.
On SNAPSHOT, my BTHH5 did not have the cheatsheet, but my BPI-R4 did.
Now, on 25.12.0-rc1, the BTHH5 has it, and the BPI-R4 has two copies...
From here:
2 Likes
Thank you, now I understand how it was switched during config migration 
1 Like
Just upgraded my GL-MT6000 from 24.10.5 to 25.12.0-rc1 without any issues using owut
Regarding switch form opkg to apk. The devs do not recommend to upgrade packages using opkg because of several reasons. Does apk has the problems? (I mean the inability to overwrite existing packages, correctly upgrading packages by not risking to crash the whole system)
Yes. The root cause is a matter of the packages having issues with how their dependencies are defined, not the package manager being used. We just need to keep pecking away at the packages that "do things wrong" now that we've got a way to fix things up, but it might take a while.
Note the first thing on all of our apk docs:
4 Likes
2 x tplink re205 v3 updated successfully as a wireless bridge.
1 Like
Alright, so as I understand it if you want to upgrade packages inside the same OpenWRT version, you just have to use Firmware Selector and ask it to build a custom image (in my case I have dnsmasq-full).
And a second question – there’s an upgrade for firewall4 package for 24.10.5 version, where do I find version history for the package?
Or use owut or LuCI Attended Sysupgrade, they do the same thing as Firmware Selector, but run the front end locally, which may be more convenient.
The firewall4 package is delivered using the rolling release model, so isn't tied to a specific OpenWrt version (you could be running 24.10.0 and still have the latest 24.10-version of the firewall). To find out what you've got, look at the installed version, grab off the hash (in this case 18fc0ead):
$ opkg info firewall4
Package: firewall4
Version: 2024.12.18~18fc0ead-r1
Then go look at the code in https://github.com/openwrt/firewall4/ and find that hash in the history to pinpoint its last update, which in this case is
https://github.com/openwrt/firewall4/commit/18fc0ead
(Same on 25.12, but you'd use apk info to get the commit version.)
To look at what's being built in the various branches, look at the makefile's history at https://github.com/openwrt/openwrt/commits/main/package/network/config/firewall4
4 Likes
root@rt-ax52:~# cat /etc/profile
[ -e /tmp/.failsafe ] && export FAILSAFE=1
[ -f /etc/banner ] && cat /etc/banner
[ -n "$FAILSAFE" ] && cat /etc/banner.failsafe
grep -Fsq '/ overlay ro,' /proc/mounts && {
echo 'Your JFFS2-partition seems full and overlayfs is mounted read-only.'
echo 'Please try to remove files from /overlay/upper/... and reboot!'
}
export PATH="/usr/sbin:/usr/bin:/sbin:/bin"
export HOME=$(grep -e "^${USER:-root}:" /etc/passwd | cut -d ":" -f 6)
export HOME=${HOME:-/root}
export PS1='\u@\h:\w\$ '
export ENV=/etc/shinit
case "$TERM" in
xterm*|rxvt*)
export PS1='\[\e]0;\u@\h: \w\a\]'$PS1
;;
esac
[ -n "$FAILSAFE" ] || {
for FILE in /etc/profile.d/*.sh; do
[ -e "$FILE" ] && . "$FILE"
done
unset FILE
}
if ( grep -qs '^root::' /etc/shadow && \
[ -z "$FAILSAFE" ] )
then
cat << EOF
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
EOF
fi
if [ -x /usr/bin/apk ]; then
cat << EOF
OpenWrt recently switched to the "apk" package manager!
OPKG Command APK Equivalent Description
------------------------------------------------------------------
opkg install <pkg> apk add <pkg> Install a package
opkg remove <pkg> apk del <pkg> Remove a package
opkg upgrade apk upgrade Upgrade all packages
opkg files <pkg> apk info -L <pkg> List package contents
opkg list-installed apk info List installed packages
opkg update apk update Update package lists
opkg search <pkg> apk search <pkg> Search for packages
------------------------------------------------------------------
For more https://openwrt.org/docs/guide-user/additional-software/opkg-to-apk-cheatsheet
EOF
fi
I believe this appeared after 25.12.0-rc1 > 24.10.4 > 25.12.0-rc1.
Will owut be able to lift my Cudy WR1300 from 24.10.5 to to 25.12.x?
1 Like
It should be able to upgrade you to 25.12
Like @hecatae says, should be no issues. I looked at the makefile for that device (https://github.com/openwrt/openwrt/blame/main/target/linux/ramips/image/mt7621.mk#L788) and it hasn't changed for 3 years, so should be smooth sailing.