Messages

Update: I installed the latest iso image over the existing one with a config restore to upgrade so I can no longer help in narrowing down this particular issue as I'm now running 26.7

The other weird part is the apparent lack of dns resolution/internet connectivity and the fact it is repeatable.

Just curious, where can you spot dns resolution and internet connectivity errors in the logs above?

Here is the healthcheck output. Nothing curious except the bin/timeout missing, but I guess this has nothing to do with the error above

Code Select Expand

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.1.11_10 (amd64) at Wed Jul 22 07:43:24 CEST 2026
>>> Root file system: /dev/gpt/rootfs
>>> Check installed kernel version
Version 26.1.11 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.1.11 is correct.
>>> Check for missing or altered base files
Missing files: 1
mtree: bin/timeout: No such file or directory
./bin/timeout missing
>>> Check installed repositories
OPNsense (Priority: 11)
>>> Check installed plugins
os-acme-client 4.16_1
os-ddclient 1.31_1
os-dmidecode 1.2
os-gdrive-backup 1.0_1
os-mdns-repeater 1.2
os-qemu-guest-agent 1.3
os-tailscale 1.4
os-tor 1.10
os-wol 2.5_4
>>> 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: .......... done
>>> Check for core packages consistency
Core package "opnsense" at 26.1.11_10 has 68 dependencies to check.
Checking packages: ..................................................................... done
***DONE***

I just tried upgrading 26.1.11 to 26.7 and after the reboot it fails and falls back to 26.1.11. I tried restoring a backup and running the whole process again, same error.

Logs:

Code Select Expand

root@opnsense:~ # opnsense-update -gG
***GOT REQUEST TO UPGRADE***
Currently running OPNsense 26.1.11_10 (amd64) at Tue Jul 21 23:52:06 CEST 2026
Fetching packages-26.7-amd64.tar: .......................................... done
Fetching base-26.7-amd64.txz: ....... done
Fetching kernel-26.7-amd64.txz: ...... done
Flushing temporary package files... done
Extracting packages-26.7-amd64.tar... done
Extracting base-26.7-amd64.txz... done
Extracting kernel-26.7-amd64.txz... done
Please reboot.
>>> Invoking upgrade script 'sanity.sh'
Passed all upgrade tests.
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Installing kernel-26.7-amd64.txz... done
***REBOOT***
Updating OPNsense repository catalogue...
pkg-static: Repository OPNsense has a wrong packagesite, need to re-create database
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries:
pkg-static: wrong architecture: FreeBSD:15:amd64 instead of FreeBSD:14:amd64
pkg-static: repository OPNsense contains packages with wrong ABI: FreeBSD:15:amd64
Processing entries...
Unable to update repository OPNsense
Error updating repositories!

Having the same question (and also that weird sysctl behaviour where the values do not match): https://forum.opnsense.org/index.php?topic=51617.0

Hi,
I've been a OpnSense user since a long time and there were a lot of version migrations. Today I had a look at the System->Settings->Tunables view and there are a lot of items where the current value differs from the default (although I never changed any of them).
I am now wondering if those are all old default values that have been set to a new default in the meantime, or if some configuration changes also trigger value changes in the Tunables section.
So should I change the Values to their new Default value, or will this break any existing configurations that rely on those values?