OPNsense Forum

English Forums => 26.1, 26,4 Series => Topic started by: OzziGoblin on June 05, 2026, 06:46:57 AM

Title: Cleaning up old Tunables
Post by: OzziGoblin on June 05, 2026, 06:46:57 AM
Hi everyone

I've recently looked at the list of tunables that I have, and there are 63.  Looking at the documentation on https://docs.opnsense.org/manual/settingsmenu.html#tunables there are a lot less.

Is there a list of the required tunables so that I can delete any old ones left over from inplace upgrades?

thanks
Title: Re: Cleaning up old Tunables
Post by: franco on June 05, 2026, 08:01:25 AM
Since a while there are no default tunables in the configuration so theoretically you could delete all of them.

However, depending on what the hardware or software requires you could still have some that you added and want to keep.


Cheers,
Franco
Title: Re: Cleaning up old Tunables
Post by: OzziGoblin on June 05, 2026, 11:31:19 AM
Thanks @franco
Title: Re: Cleaning up old Tunables
Post by: dinguz on June 05, 2026, 07:15:35 PM
If default tunables have been removed from the codebase for some time now, why does my current config still show roughly 60 entries without a delete icon?
Are these considered user-defined tunables that OPNsense simply cannot distinguish from defaults, or is the missing bin icon a UI bug / a sign that they are still treated as system-owned?
Title: Re: Cleaning up old Tunables
Post by: franco on June 05, 2026, 11:32:21 PM
Basically, yes, but it's complicated.

In the old days almost all sane defaults were set from the config.xml, but that was a persistence issue across versions if these values needed to change. Some sysctls were set opportunistically from unrelated components for related reasons, too.

Since a number of years these defaults went out of the config.xml into a "softcoded" list of default tunables that are required by the system even though they are not set by the config. Adding them to the config (and overriding them) is possible, but in most cases that's unneeded.

So eventually we removed all config.xml bound sysctls from the community defaults without losing the ability to steer required tunables with default values in any case.


Cheers,
Franco