—
—verified
—
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.
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-diveIntegrity 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
—
—
03 · INTEGRITY
Verify before deploy.
The .sha512 manifest sibling lets you confirm the script body matches what mikrotikfilters served, on your workstation, before /import-ing on your router. The check runs off-router — the router itself relies on TLS with check-certificate=yes. 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.
sha512 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).
—
Community-maintained. The original author is no longer an active supporter; the script remains available because contributions belong to the community once approved. Only moderators can take this script down.
Verified by moderators. A mikrotikfilters moderator has read this script's current body and confirmed it does not contain known malicious patterns at verification time. Edits require a fresh review — the author proposes changes via the edit-request flow, and the verified flag clears on approval until the new body is re-verified.Verification is a sanity check, not a formal audit;always read the body yourself before /import. See /docs/threat-model §3.5for the full moderation posture.
Loading…
Script not found. Back to catalogue.
Could not load script. Reload to retry.