Devices

The Devices section is where you browse the firewalls in the active organization, dig into any one of them, and trigger device-level actions like sync, restart, or open a remote terminal.

Devices list

Each row is one enrolled device:

Column	Meaning
Name	Friendly name set at enrollment. Click it to open the detail page.
Status	Enabled, Pending (awaiting admin approval), or Disabled.
OUs	Every organizational unit the device belongs to.
Version	Reported NDAgent version. Drift between devices is a hint to plan an update.
Last Heartbeat	How long ago the device checked in. A long gap means the device is offline.
Drift	Whether the device’s running configuration matches what NetDefense last delivered. Values: IN_SYNC, DRIFT, NEVER_SYNCED, UNKNOWN, ERROR. See Drift Detection.

The filter bar above the table accepts a name substring and dropdowns for status, OU, and drift status. The … menu on each row exposes per-row actions: Approve, Rename, Delete.

Read about device approval, identity, and the v=2 rebind flow in Device Identity.

Device detail

Clicking a device opens its detail page. The header shows the device name, an online badge (online, offline, or unknown while the page can’t refresh), its status badge, when the device was created and last updated, and the action buttons:

• Approve (pending devices) — approves the device.
• Connect (enabled devices) — opens the browser-based access screen with a terminal and WebAdmin proxy for this device.
• Sync (enabled devices) — pushes the current computed configuration to the device. The action is also available in bulk from the Synchronize page.
• Delete — Permanently deletes the device. On its next contact the device removes all NetDefense-managed configuration (firewall rules, aliases, VPN, users, external authentication servers, certificates and CAs, package repositories) except certificates and CAs still in use by a service, uninstalls the NetDefense agent and repository, and cannot be restored. Re-adding it requires a fresh installation. It also can’t be re-bound. See Remove a Device for the full behavior, including what to check first if you rely on this device for remote access.

Live telemetry

The Live telemetry panel at the top shows the device’s latest report and refreshes every 30 seconds. Click its title to collapse it.

• Device — name, agent version, OPNsense version, and sync state.
• Resources — uptime, CPU count, load, memory, and swap.
• Disks — usage per mount point.
• Pending updates — the OPNsense verdict, as on the Dashboard, with where its “latest” came from; the agent version against the latest release; how many packages are pending; reboot required when the pending updates need a reboot; and when the device last checked for updates.
• Services — the monitored services that aren’t running, with every service under All services.
• Certificates — each certificate with its expiry date, flagged when it has expired or expires within 30 days.

When data is missing or old:

• A device that’s offline, or hasn’t reported for about 3 minutes, keeps its last report on the page for up to 7 days, with a note such as Showing the last report, received 12m ago. The device is offline. The Resources, Disks, Pending updates, Services, and Certificates cards are faded and dated (as of 12m ago). Pending updates, Services, and Certificates also fade when their reading is more than 35 minutes old.
• The OPNsense version reads (last report) or (reported at connect) when it doesn’t come from a current report.
• A card without data says Not collected yet., and so does the whole panel when the device has no report at all. Pending updates says All packages up to date. only after a completed update check: before the first one it says No check completed yet., and after a failed one, The last check failed.
• If the page can’t refresh, it keeps the data it has, the online badge reads unknown, and the panel gives the time of the data shown.

Other cards

• Facts — hostname, timezone, OPNsense and operating system versions, and interfaces, as the device reports them. Informational only; the card is hidden until the device reports any.
• Drift Status — last heartbeat, last successful sync, and current drift status, with when drift was last checked.
• Organizational Units — the OUs this device belongs to, with chip-style removers and an Add to OU… picker.
• Variable Overrides — variables overridden specifically for this device. Click Add Override to override an organization-level variable for this device only; the pencil and trash icons edit and remove existing overrides. See Variables for the full scoping model.
• VPN Networks — every overlay network the device is a member of, with its overlay IP and a HUB/SPOKE badge.