Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - ezhik

#1
26.7 Series / Re: Cicada theme
July 16, 2026, 05:35:36 AM
Theme needs an update, OPNSense Dark Theme is not bad. Try that in the interim.
#2
26.7 Series / Re: 26.7 showing missing dependencies
July 15, 2026, 11:09:21 PM
Hey Franco,

No stress mate. I really appreciate you and the work that you guys do. Genuinely, thank you!

Sorry for being a pain in the butt, I mean well :)

#4
26.7 Series / Re: 26.7 showing missing dependencies
July 15, 2026, 07:30:06 PM
Quote from: franco on July 15, 2026, 12:51:17 PM# pkg remove php83-pecl-mongodb

I think many of us ran into the same issue, this helps with this problem. But now we have plugins listed as orphaned... Is that normal?


os-ddclient (orphaned) 1.31_1 192KiB 4 OPNsense Dynamic DNS client
os-isc-dhcp (orphaned) 1.0_6 284KiB 4 OPNsense ISC DHCPv4/v6 server
os-qemu-guest-agent (orphaned) 1.3 18.9KiB 4 OPNsense QEMU Guest Agent for OPNsense
os-sensei (orphaned) 2.6.1 328MiB 4 SunnyValley Zenarmor is an Enterprise SASE & SSE platform (NGFW, SWG, CASB, ZTNA, SD-WAN)
os-sensei-agent (orphaned) 2.6.1 178MiB 4 SunnyValley Cloud Connectivity Agent for Zenarmor - Enterprise SASE & SSE platform
os-sensei-updater (orphaned) 2.0 3.75KiB 4 SunnyValley OPNsense ZENARMOR Plugin Updater
os-sunnyvalley (orphaned) 1.5_2 2.43KiB 4 OPNsense Vendor Repository for Zenarmor - Enterprise SASE & SSE platform (NGFW, SWG, CASB, ZTNA, SD-WAN)
os-theme-cicada (orphaned) 1.41_1 5.31MiB 4 OPNsense The cicada theme - dark grey onyx
os-theme-rebellion (orphaned) 1.9.4 5.23MiB 4 OPNsense A suitably dark theme
os-theme-tukan (orphaned) 1.31 5.29MiB 4 OPNsense The tukan theme - blue/white
os-theme-vicuna (orphaned) 1.51 5.31MiB 4 OPNsense The vicuna theme - blue sapphire

#5
26.1, 26,4 Series / Re: 26.1.4 - Unexpected Error
March 11, 2026, 05:40:33 PM
Quote from: franco on March 11, 2026, 02:45:54 PMOkay, fair.


Cheers,
Franco

Gentle chuckle. Thank you.
#6
26.1, 26,4 Series / Re: Upgrade went wrong
March 10, 2026, 02:49:53 AM
Quote from: newsense on March 10, 2026, 02:25:36 AMReinstall elastic with

# pkg install -f elasticsearch8


The rest looks good.

DONE:

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.1.3 (amd64) at Mon Mar  9 21:46:57 EDT 2026
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 26.1.3 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.1.3 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
SunnyValley (Priority: 7)
>>> Check installed plugins
pkg: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
os-ddclient 1.30
os-isc-dhcp 1.0_4
os-qemu-guest-agent 1.3
os-sensei 2.4.1
os-sensei-agent 2.4
os-sensei-updater 1.18
os-sunnyvalley 1.5_2
os-theme-cicada 1.41
os-theme-rebellion 1.9.4
os-theme-tukan 1.31
os-theme-vicuna 1.51
>>> Check locked packages
pkg: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
>>> Check for missing package dependencies
pkg: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
Checking all packages: .......... done
>>> Check for missing or altered package files
pkg: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
Checking all packages: .......... done
>>> Check for core packages consistency
Core package "opnsense" at 26.1.3 has 67 dependencies to check.
Checking packages: .................................................................... done
***DONE***

#7
26.1, 26,4 Series / Re: Upgrade went wrong
March 10, 2026, 02:07:01 AM
Quote from: newsense on March 10, 2026, 01:29:35 AM
Quote from: ezhik on March 10, 2026, 01:01:44 AMWhat do you mean a manual complication? I did not install it manually. I run vanilla OPNSense.

OPNsense has extensive check to make sure the FreeBSD repos are disabled.


The fact you ended up with pkg from FreeBSD instead of the one from OPN means that the system was modified on purpose by "something" which in turn pulled packages from FreeBSD. This is why you're seeing the db version mismatch after you reverted pkg to the one in OPN.

The db warning is not catastrophic to my knowledge so you can continue to use the system as is.


More importantly though it may be possible to have there other packages from other repos that may cause trouble in the future.


For now it would be best to post here an audit so we can get a better understanding of where you're at.

It is weird indeed...

Attaching "audit: health"

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.1.3 (amd64) at Mon Mar  9 21:05:23 EDT 2026
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 26.1.3 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.1.3 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
SunnyValley (Priority: 7)
>>> Check installed plugins
pkg: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
os-ddclient 1.30
os-isc-dhcp 1.0_4
os-qemu-guest-agent 1.3
os-sensei 2.4.1
os-sensei-agent 2.4
os-sensei-updater 1.18
os-sunnyvalley 1.5_2
os-theme-cicada 1.41
os-theme-rebellion 1.9.4
os-theme-tukan 1.31
os-theme-vicuna 1.51
>>> Check locked packages
pkg: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
>>> Check for missing package dependencies
pkg: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
Checking all packages: .......... done
>>> Check for missing or altered package files
pkg: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
Checking all packages:
elasticsearch8-8.11.3: checksum mismatch for /usr/local/lib/elasticsearch/lib/jna-0.0.0.jar
Checking all packages............. done
>>> Check for core packages consistency
Core package "opnsense" at 26.1.3 has 67 dependencies to check.
Checking packages: .................................................................... done
***DONE***

#8
26.1, 26,4 Series / Re: Upgrade went wrong
March 10, 2026, 01:01:44 AM
Quote from: franco on March 09, 2026, 08:57:28 PM> This update is a bit rough for many, hopefully there is an update to patch things up.

Yes, but we did establish it's rough because the wrong package manager ended up installing which is a manual complication we neither test nor can control.


Cheers,
Franco



What do you mean a manual complication? I did not install it manually. I run vanilla OPNSense.
#9
26.1, 26,4 Series / Re: Upgrade went wrong
March 07, 2026, 10:31:30 PM
This update is a bit rough for many, hopefully there is an update to patch things up.
#10
26.1, 26,4 Series / Re: Upgrade went wrong
March 06, 2026, 10:41:15 PM
Quote from: franco on March 06, 2026, 08:03:29 PM# opnsense-revert opnsense


Cheers,
Franco

What is expected here? Doesn't look like it worked as expected either:


root@opnsense:~ # opnsense-revert opnsense
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: 100%    179 B   0.2kB/s    00:01   
SunnyValley repository is up to date.
All repositories are up to date.
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
The following packages will be fetched:

New packages to be FETCHED:
        opnsense: 26.1.3 (6 MiB: 100.00% of the 6 MiB to download)

Number of packages to be fetched: 1

The process will require 6 MiB more space.
6 MiB to be downloaded.
Fetching opnsense-26.1.3.pkg: 100%    6 MiB   6.1MB/s    00:01   
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
opnsense-26.1.3: already unlocked
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: 100%    179 B   0.2kB/s    00:01   
SunnyValley repository is up to date.
All repositories are up to date.
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
        opnsense-26.1.3 [OPNsense]

Number of packages to be reinstalled: 1
[1/1] Reinstalling opnsense-26.1.3...
[1/1] Extracting opnsense-26.1.3: 100%
Stopping configd...done
Resetting root shell
Updating /etc/shells
Unhooking from /etc/rc
Unhooking from /etc/rc.shutdown
Updating /etc/shells
Registering root shell
Hooking into /etc/rc
Hooking into /etc/rc.shutdown
Starting configd.
>>> Invoking update script 'refresh.sh'
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense SunnyValley
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from opnsense-26.1.3:

--
One step ahead, one step behind it, now you gotta run to get even
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
#11
26.1, 26,4 Series / Re: Upgrade went wrong
March 06, 2026, 07:11:56 PM
Quote from: franco on March 06, 2026, 06:57:40 PMYou installed the FreeBSD package manager version, which isn't good.

>   opnsense-26.1.3 [OPNsense] (Vital flag changed: 'true' -> 'false')

This looks like a weird database bug. Vital flag is never removed.

Try this first...

# opnsense-revert pkg


Cheers,
Franco

Did not work.

Had to:
# cd /tmp
# curl "https://pkg.opnsense.org/FreeBSD:14:amd64/26.1/MINT/26.1.3/latest/All/pkg-2.3.1_1.pkg" --output pkg-2.3.1_1.pkg
# pkg install pkg-2.3.1_1.pkg
# opnsense-revert pkg

How do we fix the "Vital" flag now?
#12
26.1, 26,4 Series / Re: Upgrade went wrong
March 06, 2026, 06:46:24 PM
Exactly same thing happened to me. I rebooted after that and it was fine.

EDIT: actually no. check for updates reports a segmentation fault for one of the packages.

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.1.3 (amd64) at Fri Mar  6 12:52:54 EST 2026
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data: ....... done
Processing entries: .......... done
OPNsense repository update completed. 931 packages processed.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching data: .. done
Processing entries: .. done
SunnyValley repository update completed. 15 packages processed.
All repositories are up to date.
Child process pid=88379 terminated abnormally: Segmentation fault
Upgrading package manager from version '2.5.1' to '2.3.1_1'
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
OPNsense is up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Child process pid=99031 terminated abnormally: Segmentation fault
Checking for upgrades (198 candidates): .......... done
Processing candidates (198 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***
#13
General Discussion / Re: website update looks great!
December 25, 2024, 07:00:34 PM
+1 for Dark Mode
#14
General Discussion / Re: Forum Theme: Dark Mode?
December 25, 2024, 07:00:14 PM
Thanks!
#15
General Discussion / Forum Theme: Dark Mode?
December 25, 2024, 05:17:40 AM
I can't seem to find it, does it exist? The default seems way too bright.