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

Topics - fakemoth

#1
Hi, as you can see from my "activity" I didn't have a lot of problems with OPNSense. Except now when upgrading to 26.1.3, the installation had an error but it seemed to continue. After reboot, got a boot loop with text just scrolling fast on the screen. I tried loading a new kernel = nothing. I tried restoring a snapshot = nothing only another error running on the screen. That was an ugly surprise, I am used to snapshots restoring stuff in ZFS.

So I reinstalled figuring "hey should be easy to restore 'cause you have backups". But no, had to do a full install, juggling 3 cables in 4 nics (because nothing is displayed when connecting something, to see what interface becomes damn active), got on the default IP, restored. Again - no, you dont't have all the cables properly plugged - so I plugged them - oh no, you lost connectivity, so on. The circus around a restore is quite maddening.

After several reboots, I restored... something and everything seemed in place. Yes! But again - no: I don't have the plugins. So I went to System > Firmware > Plugins, and they were in red all right. Tried to install, but:

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 26.1.2_5 (amd64) at Sun Mar  8 12:42:28 EET 2026
>>> Root file system: zroot/ROOT/default
>>> Check installed kernel version
Version 26.1.1 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 26.1.1 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
>>> Check installed plugins
No plugins found.
>>> 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.2_5 has 67 dependencies to check.
Checking packages: .......
dnsmasq-2.92,1 version mismatch, expected 2.92_2,1
Checking packages: ................
opnsense-26.1.2_5 version mismatch, expected 26.1.3
Checking packages: .
opnsense-installer-25.1_1 version mismatch, expected 25.1_2
Checking packages: ..
opnsense-update-26.1.1_1 version mismatch, expected 26.1.3
Checking packages: ......................
py311-Jinja2-3.1.6 has no upstream equivalent
Checking packages: .
py311-dnspython-2.8.0_1,1 has no upstream equivalent
Checking packages: .
py311-duckdb-1.4.4 has no upstream equivalent
Checking packages: .
py311-jq-1.11.0 has no upstream equivalent
Checking packages: .
py311-ldap3-2.9.1_1 has no upstream equivalent
Checking packages: .
py311-numpy-1.26.4_12,1 has no upstream equivalent
Checking packages: .
py311-pandas-2.3.3,1 has no upstream equivalent
Checking packages: .
py311-requests-2.32.5 has no upstream equivalent
Checking packages: .
py311-sqlite3-3.11.14_11 has no upstream equivalent
Checking packages: .
py311-ujson-5.11.0 has no upstream equivalent
Checking packages: .
py311-vici-6.0.3 has no upstream equivalent
Checking packages: .......... done
***DONE***

So now I am supposed to get to 26.1.3 to have plugins?

Sorry to sound bitter, but I am not a networking expert so it took me a long time to have 13 VLANS, NGINX proxy, adblockers, blacklists, dual wans, policies and lots of firewall rules.

I restored a bunch of other OSes, switches, VMs, NASes, and even pfsense that I was using before, quite a lot of stuff. Never before I was more perplexed at restoring something, without internet of course - so if you guys could something to improve on that, to streamline it and so on - it would be great.

Now, what can I do about messages like these, when trying to install NGINX, without having to again bork the system with a 26.1.3 upgrade?

***GOT REQUEST TO INSTALL***
Currently running OPNsense 26.1.2_5 (amd64) at Sun Mar  8 13:03:44 EET 2026
Installation out of date. The update to opnsense-26.1.3 is required.
***DONE***

Thank you, and please allow us to vent a bit here - this became a very ugly week-end, for quite a few people it seems.
#2
Hi, can anyone provide a link to some proper maintained IP lists for search engines (separate per search engine) for the purpose of whitelisting? Something like the raw ones from Github, using like 10 already for blocking, that can easily be added as URL ip table in aliases and used on floating?

For the life of me I can't seem to find some decent/recent ones and search engines like purposely hide them :D So what do you guys use?

Thanks!