The default config favors intel (or dis-favors my particular CPU) in that I need the setting: sysctl vm.pmap.pti=0 All updates between the first or second after switching to OPNsense and the last version prior to 19.1 were easy and trouble-free.ĮDIT: I received help with the issue and it is a simple fix. Another idea I just realized is to attempt a fresh install of vanilla Hardened BSD to see whether that succeeds or not. The update or install reaches a point where the screen goes blank and it seems to stall, so one of my last trouble-shooting options would be to try a graphics card in lieu of the integrated one. I suspect it may be *something* related to Hardened BSD since migration to HardenedBSD 11.2 was completed in OPNsense 19.x. I am still using it, and with an older bit of hardware (Asus M5A88-M with AMD Athlon II x2 270) but something about this hardware denies an update/upgrade or fresh install to the 19.1.x version. For the vast amount of time since switching to OPNsense, I have had no problems. I had also a time or two with difficulties on pfsense, updates that didn't work so smooth, or other configuration things. ![]() ![]() Then when I read what the timeline and feature plans were for OPNsense, I decided to switch since OPNsense appeared that it might reach those goals sooner. I used pfsense for a while prior to the fork.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |