First: it *was* working... then being a noob & google, I briefly enabled FreeBSD, installed something, disabled FreeBSD. I suspect that is the root of my problem, but I have no idea how to fix it. (and *think* i have since learned the correct way, but feel free to slap my hand & point me in the correct direction.)
system/firmware/update shows no issues (FreeBSD disabled):
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.1.10 (amd64/OpenSSL) at Fri Jul 22 17:05:42 EDT 2022
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 799 packages processed.
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking for upgrades (28 candidates): .......... done
Processing candidates (28 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***
The plugins list shows what I did turn on - but none of the big 'available' list. The plugins that are there - that I did install - all show as "missing".
If I enable FreeBSD, the updates shows a mix of things; of course I cancel & don't do any of it.
Please help.
thank you
Same problem to me, it started on same version and continues after upgrade to v22.7; didn't find a fix so far.
Regards
Currently when enabling the FreeBSD repository it gives you a bad version of the package manager "pkg" which also breaks your package database for the older version we still use.
I don't currently know a good way to repair this.
Eventually we want to use pkg version 1.18 but not ready to leave 1.17 behind just yet for many reasons.
Cheers,
Franco
Hi Franco,
Thanks for the info.
Regards.
Hi again,
I confirm the issue is solved after downgrading pkg to OPNsense's repository version (1.17.5_1) and locking pkg updates.
Regards.
Nice to hear. In that case something as simple as
# opnsense-revert pkg
Should fix this for others having the same issue.
Cheers,
Franco
missed this reply by "that much". LOL. I backed up the configuration & reburned the unit & restored. Things are ok now. Partial lesson learned anyway. It was good to know other people had these issues. Still a total noob on this thing, learning every day.