What is correct Kernel for 26.1.8_5?

[vk2him]

I recently updated to 26.1.8_5 and the health audit I just ran displayed the kernel is 26.1.7 - is this correct?

Code Select Expand

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.1.8_5 (amd64) at Sat May 23 19:50:23 AEST 2026
>>> Root file system: zroot/ROOT/know_working
>>> Check installed kernel version
Version 26.1.7 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.1.7 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
mimugmail (Priority: 5)
ntop (Priority: 100)
>>> Check installed plugins
os-adguardhome-maxit 1.16
os-cpu-microcode-intel 1.1
os-gdrive-backup 1.0_1
os-homeassistant-maxit 1.0
os-isc-dhcp 1.0_4
os-lldpd 1.2
os-net-snmp 1.6_1
os-ntopng 1.3
os-nut 1.9_1
os-openvpn-legacy 1.0_1
os-q-feeds-connector 1.6
os-redis 1.1_4
os-smart 2.4
os-speedtest-community 0.9_6
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: ....
os-adguardhome-maxit-1.16: checksum mismatch for /usr/local/AdGuardHome/AdGuardHome
os-adguardhome-maxit-1.16: checksum mismatch for /usr/local/AdGuardHome/AdGuardHome.sig
Checking all packages....
os-speedtest-community-0.9_6: checksum mismatch for /usr/local/opnsense/scripts/OPNsense/speedtest/opn_speedtest.py
Checking all packages........ done
>>> Check for core packages consistency
Core package "opnsense" at 26.1.8_5 has 68 dependencies to check.
Checking packages: ..................................................................... done
***DONE***


[newsense]

Yes, not every release has one.

New kernel patches will be in 26.1.9

[vk2him]

Excellent - many thanks.

I should have mentioned that my initial attempt to update to 28.1.8_5 from 28.1.7 hung, so I tried the update again from the ssh menu and it worked there.

I wondered if the aborted update had "broken" the kernel.

[newsense]

You're up and running so no.

Whenever in doubt do a health check from the firmware section.

[franco]

Incidentally, "Version x.y.z is correct." was added to the health audit to avoid this particular question, but it seems that this hint doesn't always work as intended.  :)


Cheers,
Franco

[vk2him]

Thanks Franco,

To avoid any doubt, could the message be:

"Version x.y.z is correct for OPNsense a.b.c_d" ?

Cheers

[franco]

The core version is shown 2 times in the health audit already. And the base/kernel don't follow it. That's what opnsense-update is for. And there are complications when people lock the core package or opnsense-update that would make this more wrong than it is now: it's correct from locally installed opnsense-update's version perspective.


Cheers,
Franco