Messages

No previous action log found.

Intime to install the fix 26.1.7_1 ?

Does it mean it's random in your eyes ?

Yes

franco, now is your turn.

Tell me , friends, did you got Segmantation Fault red popup ?

As fas as I understand - Yes and No. Yes, but it has to be decompressed, No - it takes additional CPU ticks.

You 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

There was an error about Segmentation Fault first, red popup.

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***

Yes, this is the real problem, maybe try to update from console ?

***GOT REQUEST TO UPDATE***
Currently running OPNsense 26.1.3 (amd64) at Fri Mar  6 19:59:05 MSK 2026
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
SunnyValley repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
SunnyValley repository is up to date.
All repositories are up to date.
Checking for upgrades (259 candidates): .......... done
Processing candidates (259 candidates): . done
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
   opnsense-26.1.3 [OPNsense] (Vital flag changed: 'true' -> 'false')

Number of packages to be reinstalled: 1

6 MiB to be downloaded.
[1/1] Fetching opnsense-26.1.3: .......... done
Checking integrity... done (0 conflicting)
[1/1] Reinstalling opnsense-26.1.3...
[1/1] Extracting opnsense-26.1.3: .......... done
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.

Stuck completely ..... while Internet connection still working after reboot.

Ну просто охренеть не встать - заработало. Перезапустил ZenArmor.

Здравствуйте господа !

Есть проблема связки - то работает, то нет,кто-нибудь сталкивался ?

Loader problem in case of mine is 100% fixed, no other problems are obvious.

Похоже, там СДС Ясенево, кекоз - полная перетряска.

Могу поделиться с Вами, коллегами, своим опытом - CrowdSec обязателен, за почти 2 года я смог, с посторонней помощью (Google), отстрелить всех, на данный момент, включая станцию дальней разведки из Ясенево. Вот уже неделю Alert список Crowdsec пустой.

ZA itself is working, verified in package Dashboard. Cloud nodes are up and running.

Quirck found - ZenArmor Dashboard is not comming up on the main screen