Skip to content

v1.2.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 24 Sep 12:34
· 25 commits to main since this release
Immutable release. Only release title and notes can be modified.
v1.2.2
This tag was signed with the committer’s verified signature.
jmrplens José M. Requena Plens
GPG key ID: FCF653391E2C91FC
Verified
Learn about vigilant mode.
1004965
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Which file do I need?

Two different programs are published here, and they run on two different
machines. Read the table before downloading anything.

I want to… Download Runs on
Install and use mikroscope (the usual case) mikroscope_1.2.2_<os>_<arch>.tar.gz — or .zip on Windows your own computer, not the router
Let the router fetch the agent nothing: mikroscope install --remote-image jmrplens/mikroscope-agent:1.2.2 the router pulls it itself
Side-load the agent image one mikroscope-agent-<arch>.tar from the table below uploaded to the router
Run the agent outside a container mikroscope-agent_1.2.2_linux_<arch>.tar.gz wherever you unpack it

The CLI archive is picked by the operating system and CPU of the
machine you type commands on: linux_x86_64 for an ordinary PC or server,
darwin_arm64 for an Apple-silicon Mac, windows_x86_64 for Windows.
Nothing about it depends on the router.

The agent image tar is picked by the router's architecture, and only
matters if you install with --agent-tar:

Your MikroTik /system/resource architecture-name Agent image tar
RB5009, CCR2004, hAP ax³, most 64-bit ARM boards arm64 mikroscope-agent-arm64.tar
hEX Refresh / hEX S (2025), any EN7562CT board arm mikroscope-agent-armv5.tar
Other 32-bit ARM boards (hAP ac², hAP ax², …) arm mikroscope-agent-armv7.tar or the v5 one
CHR, x86 RouterOS x86_64 mikroscope-agent-amd64.tar

MikroTik's container package exists for arm, arm64 and x86 only, and its
documentation states that EN7562CT boards "support only arm32v5 container
images" — an ARMv5 image runs on every 32-bit ARM MikroTik ships, an ARMv7
one does not run on those. If you are not sure which 32-bit board you have,
take the v5 tar. --remote-image avoids the question entirely: the
image index carries all four platforms and the router picks its own.

Run mikroscope doctor --router user@<address> first; it reads the
architecture off the device and says which of these it wants.

Agent image: jmrplens/mikroscope-agent:1.2.2 on Docker Hub,
which is the registry a RouterOS device is pointed at out of the box, and
ghcr.io/jmrplens/mikroscope-agent:1.2.2
(linux/amd64, linux/arm64, linux/arm/v7, linux/arm/v5).

Verify the checksums (keyless, no key to fetch); checksums.txt also
covers the agent image tars:

cosign verify-blob \
  --certificate-identity-regexp 'https://github.com/jmrplens/mikroscope/.github/workflows/release.yml@refs/tags/.*' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --bundle checksums.txt.sigstore.json \
  checksums.txt
sha256sum --ignore-missing -c checksums.txt

Full changelog: https://github.com/jmrplens/mikroscope/blob/v1.2.2/CHANGELOG.md

Assets 51
Loading