Script · mikrotikfilters

← Scripts —

—

Pull URL

—

Paste into a RouterOS /tool fetch on a daily schedule to re-pull updates after each moderator-approved edit. The body is fixed once approved — re-pulls only matter if the author submits a re-moderated update.

Slug — Versions — Submitted —

Heads up — this script is tagged for — only; you have the header toggle on the other RouterOS version. The install snippet + body below still copy verbatim, but you'll need to flip the header toggle (top-right) to verify the body shows up in this view. (CSS-hides off-version content via the same toggle the lists pages use.)

02 · QUICKSTART

Paste-and-go.

Three RouterOS commands: fetch the script body, run /import, optionally clean up the local file. For production, verify integrity from a workstation first (snippet below); the deeper-dive Integrity section covers the CI-pinning shape. Read the body below first — moderator approval is no substitute for knowing what a paste does to your router.

Step 0 (recommended) · Verify integrity from a workstation

—

install.rsc

—

03 · INTEGRITY

Verify before deploy.

The .sha256 manifest sibling lets you confirm the script body matches what mikrotikfilters served before /import-ing on your router. Body and manifest are point-in-time — fetch them as a pair (within seconds) for the digest to match. The deeper snippet below pins the digest in CI so an upstream body change refuses to deploy without an explicit operator update.

sha256 manifest URL

—

Full verify + CI-pin snippet

—

04 · BODY

Script body.

Full RouterOS source as the moderators read it. The .rsc the Pull URL serves is byte-identical to this view (plus a one-line provenance header).

—.rsc

—

05 · METADATA

Metadata.

Category: —
RouterOS compat: —
Risk level: —
Slug: —
Submitted: —

Loading…

— verified

Paste-and-go.

Verify before deploy.

Script body.

Metadata.

—