Messages

the do show up when using `pkg info` in cli.  they just don't show up in the opnsense gui > system > firmware > packages list.

i tried to force install and force upgrade both ntp and expiretable, but they still don't show up in the gui package list (but show up in `pkg info` in the cli).

how can i go back to a consistent state assuming corruption is in play?

is there a way to rebuild my package db in case it was corrupted?  it has me worried that ntp and expiretable still don't show in the gui.

ntp and expiretable doesn't show in the gui packages list even after force installing them.  they were up to date though.

ok, i manually diff'd `pkg info` output vs what's listed in the gui packages list.  mostly, there are missing things from the pkg info output side.  but the gui list is missing ntp and expiretable.

my setup is so old, i don't quite remember.  after i `pkg -f install`ed it, it's showing up in my packages list in the gui.  weird.

is there a way to see the diff between packages being shown in the gui packages list and what's actually installed?

ah!

is there an easy way to list packages that i've installed on my own (or those that are older than some date)?  i don't see rsync in the packages list in the gui, so i doubt that it was ever upgraded.

OPNsense 24.1.7_4-amd64
FreeBSD 13.2-RELEASE-p11
OpenSSL 3.0.13

rsync used to run fine, but now it fails with the following message:

Code Select Expand

ld-elf.so.1: Shared object "libcrypto.so.11" not found, required by "rsync"

i tried using the /etc/libmap.conf approach to fix it, but it doesn't work:

Code Select Expand


% cat /etc/libmap.conf
includedir /usr/local/etc/libmap.d
% cat /usr/local/etc/libmap.d/libcrypto.conf
libcrypto.so.11 libcrypto.so
% ls /usr/lib/libcrypto.so*
/usr/lib/libcrypto.so
%
% rsync
ld-elf.so.1: /usr/local/lib/libcrypto.so: version OPENSSL_1_1_0 required by /usr/local/bin/rsync not found


i've been doing updates and not doing fresh installs for the past few years.

yea, i deleted the old R3 cert.

even after getting the new R3 cert in as a cert authority, i still get tls issues when trying to check for updates in the webui...  how do you fix that?