About
A small, opinionated resource for MikroTik admins.
mikrotikfilters.com is three things bolted together: opinionated
RouterOS firewall rules with rationale,
community-curated address lists distributed as
ready-to-import .rsc files, and a moderated
RouterOS scripts library where supporters
contribute .rsc snippets other admins can pull on a
schedule.
Why it exists
Most MikroTik admins write the same handful of firewall rules from scratch every
time they bring up a new router. The good defaults are scattered across the
MikroTik wiki, forum threads, and a handful of personal blogs. We collect and
explain them in one place, and pair them with curated blocklists so you can
schedule a single /tool fetch and let your edge router stay current
without an agent.
How it differs from CrowdSec, Spamhaus, FireHOL
CrowdSec is agent-based; we're agent-less. The router fetches a static file on a schedule. Smaller signal, but no daemon and no kernel modules.
Spamhaus DROP / FireHOL are generic plain-text lists. We ship
RouterOS-native .rsc with timeouts, comments, and address-list naming
aligned with our default rules — copy-paste compatible.
Neither offers a community library of RouterOS-specific scripts. Ours is
moderated (every submission is reviewed before publication), risk-tagged,
and pull-served on the same /tool fetch + /import
shape as the address lists. See /scripts.
Who runs this
This is a solo-dev project run from Australia. It has no SLAs, no support team, and no time-based service guarantees. Hosting costs are covered by one-time support and a small monthly supporter plan; transparency shows the real numbers, and status shows the per-list ingest health.
What this site is not
- A SIEM or log-ingestion service. No telemetry leaves your router.
- Multi-vendor. RouterOS-only, intentionally — we'd rather be excellent at one thing than mediocre across five.
- A behaviour-detection agent. We are intentionally simpler than CrowdSec.
- A paywall. Every individual list at
/lists/<slug>and every approved script at/scripts/<slug>is free, forever — supporters pay for headroom (higher pull-rate caps, bundle builder, the ability to contribute scripts), not for access.
Feedback & corrections
General feedback, bug reports on the site itself, content corrections, or
"you should add a list for X" suggestions —
feedback@mikrotikfilters.com.
Plain email; no ticket system, no auto-responder. Best-effort reply when the
operator's heads-down on something else.
Two adjacent channels for specialised reports — please use the right one so the inbox stays useful:
-
Suspected security vulnerability →
/security (separate disclosure inbox + RFC 9116
/.well-known/security.txt). -
Privacy / DSAR / data-deletion request →
privacy@mikrotikfilters.com(the address documented on /privacy).