Software Policies
A software policy is a named list of OPNsense plugins and FreeBSD packages, each marked Present or Absent. Attach the policy to a template and NetDefense installs or uninstalls the matching packages on every device that template reaches during the next sync. Read the conceptual model in Software Policies.
Software Policies list
Section titled “Software Policies list”
Each row is one policy:
| Column | Meaning |
|---|---|
| Name | Click to open the policy. |
| Present | Number of packages the policy declares must be installed. |
| Absent | Number of packages the policy declares must be removed. |
| Updated | When the policy or its package list was last changed. |
Each row’s … menu has Edit, Duplicate, and Delete.
Creating and editing a policy
Section titled “Creating and editing a policy”+ New policy in the top-right opens the editor. A policy has a name, an optional description, and a list of package entries. Each entry has a package name (the FreeBSD pkg name or OPNsense plugin name) and a state — Present or Absent.
Once saved, the policy is inert until you attach it to a template. When a device synchronises with a template that includes a software policy, NDAgent computes the diff between what’s installed locally and what the policy declares, then installs or removes packages to converge. Failures surface as failed tasks on the device’s history.
Policies are organization-scoped, so the same list can be reused across multiple templates without duplication.