MikroTik Manager

3rd party tools
21

Releases · hreskiv/mikr · GitHub v1.31.0 is running :slight_smile:

https://github.com/hreskiv/mikr/discussions

New panel is available form talk :slight_smile:

22

Small update for the thread — MikroTik Manager is now listed in the official Made for MikroTik catalog:

https://mikrotik.com/mfm/software

A few highlights from the past month:

  • GeoIP firewall generator — pick countries, allowlist or blocklist mode, IPv4/IPv6, deploys the script straight to the device, with optional weekly auto-refresh. Includes safety rules so it can't lock you out of the router.
  • RouterOS CVE alerting — a Security page that matches each device's RouterOS version against the public NVD vulnerability feed and lists the CVEs that affect it (CVSS, summary, fix version, advisory link). Updated daily, dashboard banner for High/Critical, optional webhook (ntfy / Slack / Discord / n8n) when a new CVE starts affecting one of your devices.
  • Live traffic with history — RX/TX graphs per interface on the device page, with 1h / 6h / 24h / 7d ranges, hover tooltip showing the exact time and values, and a total RX/TX for the selected period (handy for LTE devices on metered plans).
  • Backups — retention policies, and every successful backup now also writes the RouterOS .rsc export to /data/exports.
  • Plus passkey sign-in, an activity audit log, a full routing-table view, and a Settings UI for the runtime config — see the changelog inside the app for the full list.

If you've got ideas or requests, I've just opened GitHub Discussions on the repo — feature ideas live in one place now and others can weigh in and vote: https://github.com/hreskiv/mikr/discussions

Domain reminder: project moved to https://mikr.app — old links to mikr.mtik.pl still resolve.

Thanks again to DATPOL for kicking this thread off and to everyone who contributed feature requests — a lot of what shipped this month started as a comment in here.

23

Hi,

First of all, thank you for creating Mikr. It has become my primary tool for managing a larger MikroTik deployment.

I have one feature idea that I think could be useful for administrators managing multiple MikroTik devices.

Since RouterOS now supports Local Update Packages / Package Server, it would be great if Mikr could optionally use this feature as an update source.

For example, the administrator could choose between:

  • Official MikroTik update servers (current behavior)
  • Local Package Server (RouterOS Local Update)

In my case, I would use a CCR2116 with an NVMe drive as the central Package Server. I would upload new RouterOS packages there once, and then let Mikr update all other MikroTik devices directly from that local repository instead of downloading packages from the Internet for each device.

This would provide several advantages:

  • Internet packages would only need to be downloaded once.
  • Faster updates over the local network.
  • Lower Internet bandwidth usage.
  • Ability to keep a tested RouterOS version locally.
  • Every device would be upgraded using exactly the same package, making updates more consistent and predictable.

I'm not suggesting replacing the current update mechanism. I simply think it would be great if Mikr could optionally use MikroTik's built-in Local Update functionality whenever it is available.

The biggest benefit wouldn't be downloading the packages themselves, but having Mikr manage the entire update process while transparently using the local Package Server. From the administrator's perspective, updating devices would work exactly as it does today—the only difference would be that the packages come from the local repository instead of the Internet.

I believe this would fit naturally into Mikr and would be especially useful for schools, businesses, ISPs, and anyone managing a larger fleet of MikroTik devices.

Just an idea from someone who manages around twenty MikroTik devices.

Thanks again for your great work!