MikroTik configuration
RouterOS from scratch or cleanup: addressing, routing, NAT, DHCP, DNS, CAPsMAN, queues. Readable exports instead of a config nobody dares to touch.
MikroTik · Network security · Infrastructure
MadCat113 Studio builds and hardens MikroTik-based networks: RouterOS configuration, firewalls, VLAN segmentation, VPN and remote access. We also audit existing setups and close what shouldn't be reachable from the internet.
Services
Six engagements we take on most often. If your task doesn't fit, we'd rather decline than learn on your production network.
RouterOS from scratch or cleanup: addressing, routing, NAT, DHCP, DNS, CAPsMAN, queues. Readable exports instead of a config nobody dares to touch.
Firewall rules that match intent, input/forward separation, management access restricted to trusted paths, service hardening, firmware and CVE hygiene.
VLANs for guests, IoT and staff. WireGuard and IPsec tunnels between sites, road-warrior access, and a clear answer to “who can reach what”.
Review of an existing RouterOS setup: exposed services, weak rules, shadowed entries, missing backups. A written report with prioritized fixes.
RouterOS logging to a central collector, uptime and link checks, scheduled config exports with off-device retention and tested restores.
VPN-only management, no exposed Winbox or WebFig on the WAN, key-based SSH, per-admin accounts. The basics, executed consistently.
Stack
The day job happens here. Anything outside the list gets flagged before we quote, not after.
BGP, OSPF, policy routing, bridge VLAN filtering, bonding, CAPsMAN wireless.
RouterOS v6 · v7 · CHR
Input/forward chains, address lists, WireGuard, IPsec, SSTP/L2TP where required, RADIUS and user-manager alternatives.
Firewall · WireGuard · IPsec
Reverse proxies, TLS, syslog collectors, uptime checks and small automation scripts that keep the network documented.
Linux · Nginx · syslog · Python
Selected work
Replaced inherited “allow all” forward rules with a documented per-site policy. Closed 40+ exposed services, kept every production link up during the rollout.
RouterOS · Firewall · VLAN
Separated guest, POS and back-office traffic with bridge VLAN filtering and CAPsMAN. Guests lost access to internal subnets; cashiers noticed nothing.
CAPsMAN · VLAN · DHCP
WireGuard tunnels between three offices and a VPN-only management path for admins. Winbox and WebFig removed from every WAN interface.
WireGuard · RouterOS · Linux
Detailed write-ups and reference configs are available on request — some clients prefer their topology to stay private.
Process
Packages
Most engagements fit one of these three. Final scope and price are always fixed in writing before the first change.
from €680
One-time review of an existing RouterOS setup.
from €1,400
Audit plus implementation of the fixes.
from €420 / mo
Monthly support for a small network team.
Words from clients
We asked for a firewall cleanup and got a two-page document explaining every rule we were keeping. Two weeks later we understood our own network better than our previous integrator ever did. — IT manager, manufacturing company
No heroic reconfigurations, no “we’ll fix it at 3 a.m.”, no surprises in the invoice. The rollout happened on a Tuesday morning and nobody outside IT noticed. — COO, retail chain
The audit report was uncomfortable to read and exactly what we needed. Half the findings were things we thought were already done. — Head of ops, services company
FAQ
MikroTik is our main focus because we know RouterOS well enough to work without surprises. We also handle Linux-based edge setups, Nginx reverse proxies and small observability stacks. If your network is Cisco, Juniper or Fortinet and you need someone to own it long term, we'll tell you honestly that it isn't our day job.
Temporary, individual accounts with a documented removal date. Prefer VPN-only management over a public IP. Credentials are rotated after the engagement and never reused across clients. We don't need permanent admin access to do the work.
Yes. Most changes are scheduled outside business hours or staged on a CHR instance first. Every change list includes a one-step rollback for each item before it's applied.
We remove it — with a comment in the config explaining why, and one line in the change log. "It's been there for years" is not a reason to keep a rule nobody can explain.
Standard mutual NDA, yes. Some of our clients prefer not to be named at all, and that's fine — the reference list is shared on request under NDA.
Fixed price per engagement for audits and hardening, monthly retainer for ongoing work. No hourly billing on small changes — it discourages people from asking questions.
Contact
A config export or a short description of the network is enough to start. If something is currently open to the internet, say so first.
Or email directly: hello@devmadcat113.xyz