网络监控项

1. Open the device's web interface and find its SNMP settings, often under Network, Services or Administration.

2. Enable SNMP v2c and note the read-only community (public on many devices).

3. If the device filters by address, allow this server's address.

4. In DumbMonit, enter the address and the community: the rest is detected automatically.

注意. A community is not encrypted on the network: on a shared network, prefer SNMP v3, which authenticates and encrypts.

1. On the device, enable SNMP and check that the community or the v3 user may read the object (the SNMP view must grant its branch).

2. In DumbMonit, enter the device address, then the community or the v3 user.

3. Fill in the object (OID) with its instance suffix, for example 1.3.6.1.2.1.1.3.0.

4. Optional: set a minimum and a maximum, or an expected text, to be warned when the value drifts.

注意. An object the agent does not know, or that its SNMP view hides, is reported down with the reason not_found.

1. WinBox or WebFig → System → Users → Groups → Add: name the group as follows and tick only the policies listed below.

   dumbmonit-read

2. System → Users → Add: create the user dumbmonit in that group, with a long random password.

   dumbmonit

3. IP → Services: enable www-ssl and pick a certificate (create one under System → Certificates).

4. Optional, to hear about new RouterOS versions: System → Scheduler → Add, interval 1d, start time startup, with this On Event script.

   /system package update check-for-updates once

5. In DumbMonit, enter the router's address (192.168.88.1) with that user name and password.

注意. RouterOS 7.1 or later is required (RouterOS 6 has no REST API); with a self-signed certificate, tick "Accept an unverifiable certificate" in the options.

1. For an API key on a UniFi OS console: UniFi Network → Settings → Control Plane → Integrations → Create API Key. Name it DumbMonit and copy it: it is shown once.

2. Or create a local account (needed for WAN and alarm status, and on a self-hosted server): Settings → Admins & Users → Create New, local access only.

   dumbmonit

3. Set that account's UniFi Network role to View Only.

4. In DumbMonit, enter the address (unifi.lan, or unifi.lan:8443 for a self-hosted server) and paste the key or the account.

5. If the network is not the default site, set the Site option to the short name shown after /manage/ or /network/ in the address bar.

注意. Use a local account, never the owner or a UI.com cloud account, and accept the console's self-signed certificate in the options unless you installed your own.

1. In the Meraki dashboard, open Organization → Settings and tick Enable access to the Cisco Meraki Dashboard API.

2. Open Organization → Administrators → Add admin and create an administrator dedicated to DumbMonit, with Organization access set to Read-only.

   [email protected]

3. Sign in as that administrator, open My profile → API access and click Generate new API key. Copy it: the dashboard shows it only once.

4. In DumbMonit, enter api.meraki.com as the address and paste the key as API key. Leave Organization empty to read the first organization the key sees.

注意. A dormant device (not seen for a long time) is counted but never reported as down, and a WAN socket without a cable is not a failed uplink: only an uplink that lost its Internet access is.

1. In the Omada controller, open Global View → Settings → Platform Integration → Open API and click Add New App.

2. Name the app as follows, choose the Client access mode and give it the Viewer role on the sites to read.

   dumbmonit

3. Click Apply: the controller shows the Omada ID, the Client ID and the Client Secret. Copy them: the secret is shown once.

4. In DumbMonit, enter the controller address (omada.lan) and the port (8043, or 443 for a hardware controller), then paste the Client ID and the Client secret.

注意. The Omada controller ships a self-signed certificate: tick "Accept an unverifiable certificate" unless you installed your own. The OpenAPI exists from controller version 5.9.

1. Sign in to HPE GreenLake (common.cloud.hpe.com) and open Manage Workspace → Personal API clients.

2. Click Create personal API client, name it as follows and choose your Central instance as the service.

   dumbmonit

3. Copy the client ID and the client secret: the secret is shown once, and HPE keeps no copy.

4. In Central, open the API gateway page (Menu → API Gateway → REST API) and note the base URL of your region.

5. In DumbMonit, enter that base URL as the address (for example us1.api.central.arubanetworks.com) and paste the client ID and the client secret.

注意. Beta: written from HPE's published API reference, not yet tested on a real Central account. It reads the new Central API with Central credentials; credentials scoped to the GreenLake platform and classic Central are not supported.

1. In the Tailscale console (login.tailscale.com), open Settings → Trust credentials → Credential → OAuth.

2. Tick only the read scope listed below, then click Generate credential.

3. Copy the client ID and the client secret (tskey-client-...): the secret is shown once.

4. In DumbMonit, enter api.tailscale.com as address and paste them as Client ID and Client secret; leave the Tailnet option empty.

注意. Only tagged devices (servers, subnet routers, exit nodes) are expected to stay online: name the ones to watch in the Devices to keep online option, or enter all.

1. Add this line to the server's configuration (server.conf, or as.conf on OpenVPN Access Server) and restart OpenVPN.

   management 0.0.0.0 7505

2. Recommended: protect it with a password, put in a file readable by the OpenVPN process alone and added as a third argument.

   management 0.0.0.0 7505 /etc/openvpn/management-password

3. In DumbMonit, enter the server's address (vpn.lan, port 7505) and the management password if one is set.

注意. Anyone who reaches the management port and knows the password can disconnect clients and reconfigure the running server: allow only the DumbMonit host in the firewall and set a password.

1. On the RADIUS server, declare the DumbMonit host as a client, with a shared secret (clients.conf on FreeRADIUS, RADIUS Clients on Windows NPS).

2. Create a test account without a second factor, and note its name and password.

3. In DumbMonit, enter the server (UDP port 1812 by default), the shared secret and the test account.

4. Optional: change the NAS identifier if the server filters requests by it.

注意. A wrong shared secret, or a host not declared as a client, usually makes the server stay silent: the check then reports a timeout.

1. Choose the device model in "Device model": it decides the commands sent, and nothing else is ever run on the device.

2. Create a read-only account on the device that may log in over SSH and show the running configuration.

3. For OPNsense through its API, create an API key for a user allowed to download backups; for PAN-OS, generate the API key of a read-only role.

4. The first SSH connection remembers the device's host key: if it ever changes, backups stop and an alert asks you to check it.

注意. Configurations hold secrets: they are stored encrypted, shown with their secrets masked, and only an administrator signed in can reveal or download them.