Kinda odd, did the "Click to check for updates" from lobby dashboard. Said it had and update to do, but got the no-repository err message. But then I just went to System-Firmware Updates tab and it showed something like 33 updates, Suricata v8 being one of them. From there the update to 25.7.6 succeeded. Not sure what to make of it. The fail message (pic) seems to suggest a "pkg update" command was needed prior to next command??
Duly noted, this is the 1st time I ever saw something odd when doing the updates from the dashboard widget.
Audit Health is good, but odd the base kernel is still 25.7.5 ??
***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 25.7.6 (amd64) at Sat Oct 25 03:29:57 UTC 2025
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 25.7.5 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 25.7.5 is correct.
From ssh
opnsense-25.7.6 OPNsense community release
opnsense-installer-25.1 OPNsense installer scripts
opnsense-lang-25.7.4 OPNsense translations
opnsense-update-25.7.5_1 OPNsense update utilities
(https://i.postimg.cc/P56s7HL3/update-fail.png)
This message is harmless and explained in the release notes. It's the "Danger" incident that seems to be more serious for some users.
As for the kernel version: OPNsense and kernel do not always match. Sometimes there is no kernel update in a new release. In that case they do not bump the kernel version number just for cosmetics.
The new package manager seems to resolve package reinstall differently: early deinstall of (vital) core package, some minutes may go past until it is readded depending on how slow or fast your disk IO is.
I'm not convinced the new behaviour is ideal. Looking at FreeBSD's pkg-base in 15.0 it may become an interesting problem to be solved in the near future.
Cheers,
Franco