Quote from: bimbar on September 07, 2026, 02:47:35 PMThere are however a few popular youtube videos pushing that scenario, which I disapprove ;) .
% git grep -i -e easy -e harmless community
community/15.1/15.1:interface. Developers are invited to check out our easy-to-use build tools.
community/15.1/15.1.10:o installer: omit swap and add noatime to root partition in quick/easy install when available space is under 30GB, fixed faulty exit on importer cancel
community/15.1/15.1.2:continue with the Easy/Quick install. This way makes sure all of the base
community/15.1/15.1.4:quick/easy install (or a custom one if you did that previously).
community/15.1/15.1.7.1:o bsdinstaller: work towards embedded installations, e.g. Quick/Easy disk selection
community/15.1/15.1.7.2:o configd: added a standard rc.d script for easy daemon control
community/15.7/15.7:import configuration tool coupled with a quick and easy installation can help
community/15.7/15.7.25:o ports: sqlite 3.10.0[10], easy-rsa 3.0.1[11], openssh 7.1p2[12]
community/15.7/15.7.25:[11] https://github.com/OpenVPN/easy-rsa/releases
community/16.1/16.1:No, we would not say it was easy getting here, but booting into 16.1
community/16.1/16.1:o backend: fix harmless error message caused by a sample template
community/16.1/16.1.3:o services: add background daemon to known services for easy reload
community/16.1/16.1.3:o services: add captive portal to known services for easy reload
community/16.7/16.7.r1:o Firewall rules category tags for easy filtering
community/18.1/18.1:o Easy-to-use update cache support for Linux and Windows in web proxy
community/19.1/19.1.r1:[5] https://hardenedbsd.org/content/easy-feature-comparison
community/21.1/21.1:open source dedication. The last 6 years were not always easy, but we
community/26.1/26.1.4:for reporting issues and testing the fixes with us to allow for easy and fastQuote from: franco on September 09, 2026, 09:27:40 AM> IIUC, someone created this thread when he found that he can not
enable or disable firewall rules after an upgrade anymore, and was
advised to install a plug-in to fix that.
Which is correct, but that's in the release notes. You don't need the
plugin to use and/or migrate the rules, but you need the plugin to
administrate them.
Quote> but I made the experience that the firewall rules didn't work after
the migration and had all to be redone
Which is entirely different. It may be because of FreeBSD 15.1 or
something else. It looks like we don't know?
Quote> Don't continue to pretend that it is an easy and harmless migration
that wouldn't even require a big fat warning. It is not.
I never pretended it was easy and harmless for you. This is the core
of the issue. It is your experience. Not everyone else's.
Quote> I wonder why that is.
Because you don't know what the problem is, but feel entitled to raise
your concern in advance? If I know your exact problem I can probably
help or point to the right bits of documentation.
Quote> However, if you use the Community Edition, I believe you also bear
some responsibility for regularly reading forum posts; otherwise,
you might find yourself facing a problem eight months down the line
that has already been thoroughly discussed and addressed. This
applies equally to experienced forum members and OPNsense newcomers.
Quote> Sometimes perhaps, but I'm surprised at the trivial questions that
are being raised seeing the code that was touched and people not
realising how many technical issues they would never notice because
a) they don't have the setup or b) changes are handled in a way that
few regressions arise to begin with.
Quote> A great example is the Intel microcode plugin that if I had read the
forum properly would have known I should have removed it before
upgrading to 26.7.
> It's a very complex issue involving the microcode updates and the
operating system that has been going on for years now -- and both
are not under our immediate influence. And here, also, it was
clearly in the release notes:
https://github.com/opnsense/changelog/blob/b0be678d6235cb8da05446df7ea233c38cdcd0a7/community/26.7/26.7#L101