Router support
What we can actually do from a terminal
Everything below is work we have done at least a hundred times, remotely, on a live link, without a site visit. Physical things — a dead port, a bent antenna connector, a plug in the wrong socket — still need hands, preferably yours.
Support matrix
| Brand | Access we use | What we do | Notes |
|---|---|---|---|
| MikroTik | OpenVPN + Winbox or API | Full config work: bridging, VLANs, queue trees, mangle, OSPF/BGP, CAPsMAN, hotspot, failover, IPv6, certificates, scheduled scripts, upgrades and rollbacks. | RouterOS 6.40+ and 7.x; SwOS for the small switches |
| Ubiquiti | SSH via tunnel, UniFi console share | EdgeOS routing and port-forward work, airOS link and channel planning, UniFi device adoption fixes, firmware pinning, controller vs. standalone decisions. | EdgeRouter X still the most supported box we know |
| Tenda | Web UI + tunnel | Everything the UI allows, plus the things it hides: firmware version pinning, guest network separation, DHCP range, channel width, and the endless /goform/ behaviour questions. | We tell you honestly what the box cannot do |
| TP-Link | Web UI + tunnel | Archer and Deco configuration, operation-mode changes, IPTV/VLAN binding, static routes on the models that allow them, mesh backhaul complaints. | Hardware version matters more than the model name |
| NETGEAR | Web UI + tunnel | Orbi and R-series cleanup, AP-mode conversion, dynamic DNS, port-forward and DMZ sanity, firmware on models that still receive it. | Older units: we mostly talk you out of remote management |
| DrayTek | Telnet/SSH + web via tunnel | Vigor multi-WAN, dial-out backup, VLAN on the LAN ports, VPN server and client, bandwidth management, the Load Balance feature people fear. | 1.5.1.x firmware questions are our daily bread |
| Zyxel | Web UI + SSH where present | USG/ATP policy work, IPSec site-to-site, hotspot ("Free Time") configuration, firmware paths that nobody reads. | 5.3x firmware generation |
| ASUS / AVM / D-Link / GL.iNet / Keenetic | Web UI + tunnel | Configuration, guest networks, VPN (OpenVPN/WireGuard where the firmware has it), and honest advice about replacement. | We do not fix what the vendor no longer ships |
| OpenWrt / generic Linux CPE | SSH via tunnel | uci config archaeology, netmigrations, LuCI breakage, package upgrades, wireguard on kernels that should not have it. | Backups before everything |
Symptom, first command, usual answer
MikroTik first because it is most of our traffic; the last three rows are what we type on other brands.
| Symptom | What we look at | Command |
|---|---|---|
| Internet drops now and then | PPPoE and uplink log, uptime per interface | /log print where topics~"pppoe" |
| Slow, but only some devices | registered clients, channel, tx/rx rates | /interface wireless registration-table print |
| One VLAN has no gateway | bridge port tagging | /interface bridge port print where bridge=bridge1 |
| Port-forward does not work from inside | hairpin NAT | /ip firewall nat print where action=masquerade |
| Someone is hammering the router | CPU, connections, service exposure | /ip service print; /system resource print |
| VPN client cannot reach the LAN | routes and NAT on the tunnel subnet | /ip route print where dst-address!="0.0.0.0/0" |
| Config reverted after reboot | the /rw partition and the factory config | /system note print; /file print where name~"reset" |
| Ubiquiti: "the controller says pending" | inform URL, device state | info; set-inform http://10.0.0.5:8080/inform |
| Tenda/TP-Link: wifi is "wrong" | channel width and band steering | UI: 2.4G → wireless → advanced |
| DrayTek: VPN up, no traffic | next hop and LAN-to-LAN policy routes | /ip route print; VPN → Dial-out Status |
What we can fix remotely
- Any configuration problem the device can be talked into describing
- Firmware upgrades, and the two-step downgrade when the upgrade was the mistake
- Wi-Fi coverage arguments, settled with the survey data your own card reads out
- Routing: static routes, OSPF neighbour flaps, BGP policy that "used to work"
- NAT, port-forwarding, DMZ, and hairpin behaviour on asymmetric ISPs
- VPNs: WireGuard, OpenVPN, IPSec, L2TP, PPTP when you are brave
- Hotspot and guest network separation, captive portal oddities
- VLAN layout, bridge membership, managed-switch trunking
- IPv6: prefix delegation from the ISP, RA, firewall, the DNS that nobody configured
- Scheduled scripts, certificates, NTP, logging that fits in a mailbox
- Security cleanup: exposed Winbox/API, default credentials, missing address-list protects
What we cannot fix remotely
- Dead hardware. A power supply is not a configuration.
- A device that drops the tunnel and the traffic together, because the tunnel rides on the traffic.
- ISP-side outages, although we will produce the evidence mail that gets you answered.
- The physical layer: a cat5e run that is really cat3, or 120 m of cable in a conduit with a fluorescent lamp.
- Firmware the vendor stopped shipping; then the honest advice is a replacement, and we will tell you which box.
- Your smart TV. It is not the router, we promise, and we can prove it.
Tooling we bring with us
- A read-only pass first: identity, resources, interfaces, addresses, routes, services, firewall, log. Nothing changes.
- A backup before every change —
/export file=pre-mikro-2026-11-16plus the full binary backup where we can take it. - Every command we run goes into the session log we mail you, including the ones that did nothing.
- Wi-Fi survey from a laptop on your LAN through the tunnel when coverage is the question.
- Long-term counters on the interfaces we suspect, sampled for a day before we call it a fix.
Also available
Network audit with a written report (EUR 180), monitoring with alerting (EUR 99 per router), and 24 vulnerability notes if you would rather read about your firmware than talk to us.
"You need help? We need access!"
One command on your side, five minutes of your time, and we can reach the router from our own terminal. If you would rather watch us work, the console is open while the tunnel is up.