Fleet monitoring — nodes phone home over a per-node bearer token, no inbound access to pfSense required.
Name
Status
Model
Version
WAN IPv4
GW
Uptime
Actions
Lines connect nodes with a resolved site-to-site VPN peer (matched by WAN IP). Color reflects the most-alive tunnel status between that pair.
UpUnknownDown
pfsense-dashboard — self-hosted fleet monitoring
Node created — save this now
The token below is shown once. It's embedded in the install script below.
If you lose this, you'll need to rotate the token (which breaks the currently-installed node
until it's reinstalled with the new script).
Name:
Token:
Copy the downloaded script to the pfSense box and run it as root
(Diagnostics > Command Prompt, or SSH):
sh install-<name>.sh
Uploads and runs the install script over SSH. The password is used once for this
connection only and is never stored.
This connection does not verify the target's host key — only use it on a network you trust. The offered key's fingerprint is recorded in the log below once connected.
Batch deploy from CSV
Columns, in order: Node Name, IP Address, Port, Username, Password. The first row is
treated as a header and skipped. Each row creates a node and deploys the install script
to it over SSH; a failed row doesn't stop the rest.
These connections don't verify the target's host key — only use this on a network you
trust. Each password is used once for its connection and is never stored.