The Devices page brings together the status, identity, and syslog configuration of every firewall connected to izgate in one place. Devices automatically recognized by serial number — FortiGate and MikroTik — are shown with live CPU/RAM/session metrics.
The Devices page isn't just an inventory list; it's the hub for managing every device's identity, syslog target, and — on supported devices — live status.
On devices that carry a serial (FortiGate/Sophos/Palo Alto), device identity is the serial number, not the IP; the address is learned automatically from the first log, so entering a syslog IP isn't required. Drivers without a serial (MikroTik, pfSense, OPNsense, generic) need an address entered.
On these two API-connected drivers, CPU, RAM, and session count are sampled every minute and shown as ring charts on the card. Other drivers don't have these metrics.
Verifies the connection, the certificate fingerprint (TOFU pinning), and the serial number match with one button. A FortiGate-specific "fix session setting" button prevents guests from dropping early during handover when the idle timeout is too short.
The three-dot menu on each card offers Edit, Log Forwarding, API Test, Remove license, Disable, and Delete.
Opens automatically right after a new device is registered: the syslog target and ports (UDP 5514, TCP 5515, TLS only if a certificate is defined), RADIUS ports (1812/1813), and a ready-made CLI/step list per driver.
For MikroTik devices registered with RouterOS 7 REST credentials, the panel automatically applies syslog, hotspot, login page, CAPsMAN Wi-Fi, and Let's Encrypt steps. Tested against a simulated RouterOS; field testing with a real device is still pending.
The Edit screen opens as a panel from the right; it starts with the required Name, Driver, and Serial Number fields. The Location section has a location name and latitude/longitude; the Syslog section has Syslog IP, Syslog Identity, and Management IP; the Verification section has a Verification Path (e.g. "Firewall API (recommended)") and an API address. A link in the panel jumps straight to the Log Forwarding screen.
The panel shows the Syslog Target (e.g. wifi.izgate.com) at the top along with UDP 5514 and TCP 5515 badges. Below, the Syslog section lists the address and port details, and the RADIUS section lists the address, the Authentication Port (1812), and the Accounting Port (1813), each as a field you can copy individually. Further down, the "Device Configuration" section lets you pick a driver (e.g. FortiGate) and switch between UDP/TCP options to generate a ready-made CLI command block (e.g. config log syslogd setting); a copy button pastes the command straight into your firewall.
Register the device by entering a name, driver, and serial number (or an address, for drivers without a serial).
The panel that opens right after registration gives you the syslog target and a driver-specific ready-made configuration.
Apply the CLI commands or step-by-step instructions in the device's own management interface.
The address is learned automatically once the first log arrives (on devices with a serial); on API-connected devices, "API Test" verifies the connection, certificate, and serial match.
No, for devices that carry a serial number (FortiGate, Sophos, Palo Alto); device identity is the serial number, and the address is learned automatically from the first incoming log. Drivers without a serial (MikroTik, pfSense, OPNsense, generic syslog) require an address.
Only API-connected FortiGate and MikroTik devices; metrics are sampled every minute. Other drivers don't have these indicators.
It verifies the connection to the device, the certificate fingerprint pinned via TOFU, and the serial number match; on FortiGate it also offers an option to fix the session (idle timeout) setting.
The setup flow (syslog, hotspot, login page, CAPsMAN, Let's Encrypt) has been tested end to end with unit tests and a simulated RouterOS, but hasn't yet been tried in the field with a real RouterOS device. The FortiGate path — both logging and the firewall API — has been verified end to end on a real device.
The three-dot menu on each card offers Edit, Log Forwarding, API Test, Remove license, Disable, and Delete.
Configure izgate Cloud based on your number of firewall devices and storage needs; no setup, get started in minutes. Call us with any questions.
