In MikroTik RouterOS, which includes CAPsMAN (Controlled Access Point system Manager), there is no specific built-in functionality that automatically registers and maintains a long-term history of devices connected to the network in the same way that a Ubiquiti UniFi controller does. .

However, it is possible to implement workarounds to achieve similar tracking by collecting data and logging events.

Alternative Solutions for Historical Recording

1. RouterOS Logging: RouterOS has very versatile logging capabilities that can be configured to log different events, including the association and disassociation of clients to CAPsMAN. You can direct these logs to a file within the MikroTik file system or export them to an external Syslog server for analysis and long-term storage.
   • Logging Settings: You can configure MikroTik's logging system to include events related to Wi-Fi, CAPsMAN, or DHCP (to see which devices get IP addresses, for example).
   • Export to Syslog: Setting up an external Syslog server and directing MikroTik logs there allows for more efficient storage and makes data analysis easier.
2. Scripting in RouterOS- MikroTik RouterOS has a powerful scripting system that can be used to create custom scripts. These scripts could, for example, collect information about connected clients at regular intervals and save that data to a file or send it to an external server for storage and analysis.
3. External Monitoring Tools: Integrating MikroTik with external network monitoring and management tools (such as Zabbix, PRTG, or Grafana with Prometheus) can provide a detailed view of the status of the network and connected devices. These tools can collect data through SNMP, RouterOS API, or custom scripts to maintain a history of connected devices and their activity.
4. MikroTik Dude: The Dude, MikroTik's network monitoring software, can be used for some aspects of network tracking and monitoring, although its focus is more on the health and status of the network than on specifically tracking clients over time. over time.

Considerations

While these solutions can provide valuable information and a historical record of network activity and connected devices, implementing them effectively may require advanced knowledge of RouterOS, networking, and possibly scripting.

Additionally, storing and processing this data long-term may require additional infrastructure, such as database servers or log storage systems.