support.mikro.strouter help over vpn
since 2014 Contact us now

About

Yuri "Support" O., and a shelf of routers that did not make it

The company is a MikroTik hAP in a Bucharest flat, an idea about doing one thing properly, and a lot of mail. We started in 2014 because a friend's internet was broken for the fourth time and nobody wanted to admit it was a firewall rule.

Nothing here is a platform. There is no dispatch board, no tier 1, no knowledge base you have to register for. You write, we read it, we ask for a tunnel, and we fix the thing — and if it cannot be fixed from a terminal, we say that in the same mail as the invoice.

Support sessions, by year
YearSessionsNote
201438one hAP, one friend, word of mouth
201576VAT registration, first monitored site
2016104the blog starts, with a Winbox CVE
2017131the Mirai year: remote management everywhere
2018149CVE-2018-14847, forty-six routers in three weeks
2019168first UniFi-heavy customers
2020201everyone discovers their home network
2021213the DrayTek years begin
2022226most sessions ever in one year
2023219TP-Link stok, again and again
2024208SwOS joins the list
2025181firmware upgrades finally boring
total1 9142026 adds 174 so far, November nearly over

Who answers

Yuri O. — the routing

Writes the commands, keeps the CVE list, owns the phrase "let me look at the log first". MikroTik since RouterOS 5, and stubbornly reads vendor release notes even when they are eleven years old and written in three languages.

yuri@mikro.st — yes, that address works, it is the same person who set up the mail server for this site and then wrote a page about why you should not host your own.

Diana — the paperwork

Invoices, scheduling, monitored-site contracts, and the only person here who reads Romanian fiscal updates out loud. If your mail about a €29 tunnel setup got an answer in four minutes on a Saturday, that was not routing skill, that was her.

The alias info@support.mikro.st goes to both of us; ops@support.mikro.st goes to the monitoring alerts, which is a polite way of describing a phone in a pocket.

Shelf, currently

Test units and spare stock. If your device is on this list we have probably broken it on purpose at least once, which is the cheapest way to learn where the "apply" button really writes.

hAP ac²ROS 7.21.2
RB5009UG+S+INROS 7.22.3
RB4011iGS+ROS 7.21.2
RB951G-2HnDROS 6.49.18
CRS326-24G-2S+SwOS 2.19
hAP liteROS 6.48.6
EdgeRouter XEdgeOS 2.0.9-hotfix.6
UDM ProUniFi OS 4.x
U6-LR6.6.71
Tenda AC18V16.03.05.11
Tenda AC6 V5V02.03.01.110
Archer AX211.1.4 Build 20230219
TL-WR940N v43.20.x
R70001.0.11.100
Vigor29601.5.1.7
USG FLEX 2005.37 Patch 1
RT-AX553.0.0.4.386
FRITZ!Box 7530FRITZ!OS 7.50
DIR-610EOL, kept for museum work
GL-MT3000OpenWrt 23.05

Last incidents we handled

The honest table: what broke, how long we took, and what it turned out to be. Monitored sites are marked; the rest came in as mail with a subject line like "internet is down again".

DateSiteReportedCauseResolve
2026-11-18Cabana Aries (monitored)pppoe flapping at 04:12ISP-side BRAS maintenance; the router did nothing wrong2 min auto
2026-11-14Office Pipera"wifi is slow on the laptop"20 MHz forced on 2.4 GHz by a guest-network rule from 201912 min
2026-11-09Atelier VR (monitored)alert: config hash changedan apprentice added a virtual AP at 18:441 mail
2026-11-02Tenda Guesthouseguests cannot printclient isolation on the guest SSID, working as designed, undocumented9 min
2026-10-27Sediul VigorVPN up, no trafficmissing return route after the 1.5.1.6 to 1.5.1.7 upgrade17 min
2026-10-15Ferma Sudswitch unreachableSwOS management VLAN removed by an update; no CVE involved22 min
2026-10-03Cluj Cabinetone AP "pending"inform URL still pointing at a controller that moved in 20246 min
2026-09-22Podul Noualert: cpu 91 %a loop through a switch in a cupboard, and the storm control nobody enabled31 min
About the dates. The vulnerability notes on this site carry the date the advisory was published, not the date we wrote about it — that is why the blog looks older than our last firmware upgrade, and why an entry about a 2010 Ubiquiti bug is still useful to somebody in Mureş with a Nanostation on a roof.

Opinions, held firmly

  • A router you can read is a router you can fix. Documentation over dashboards.
  • Remote management on the WAN interface is a decision, not a default, and usually the wrong one.
  • Firmware updates are maintenance, not risk — the risk is updating the one box in the house that has no backup config.
  • Two subnets is a network; twelve VLANs and no diagram is a hobby.
  • A tunnel on the router, not on a laptop, solves most of what people call "VPN problems at home".
  • Monitoring is expensive until the second alert. Then it is a line item.
  • If the vendor's own response to a CVE is "we do not consider this a vulnerability", the fix is a firewall rule and a phone call.
  • The password you cannot remember is the one that was changed by an update.