VPN access · how we get in
Your router calls us. We do not call it.
Support works because we can run commands on your box from ours. Instead of opening a port to the
whole internet, your router dials one OpenVPN tunnel out to our server at
support.mikro.st:1194/udp, and that is the entire arrangement. Behind CGNAT it is not a preference,
it is the only option — and OpenVPN is in the firmware of practically everything, including the cheap
boxes, which WireGuard often is not.
"You need help? We need access!"
The commands, on MikroTik
Three files and one interface. We send you the CA certificate, a client certificate and its key — named after your site, so you always know whose tunnel it is — you drop them on the router and paste this in a terminal. Nothing on our side has to be configured by you, and the tunnel IP is handed out by us, so there is no address to plan.
# 1. put the three files we mailed you in the certificate store
/certificate import file-name=mikro-support-ca.crt
/certificate import file-name=office-hap.crt
/certificate import file-name=office-hap.key
# 2. the tunnel: your router dials out, we never dial in blind
/interface ovpn-client add name=ovpn-support mode=ip client=yes \
connect-to=support.mikro.st port=1194 protocol=udp \
user=office-hap password=<the one we issue> \
certificate=office-hap_0 verify-server-certificate=yes \
cipher=aes256-cbc auth=sha1 add-default-route=no
# 3. check it, and see the address you were given
/interface ovpn-client print detail
/ping address=10.44.9.1 interface=ovpn-support count=3
# done with us for now? one command and we are outside again
/interface ovpn-client set ovpn-support disabled=yes
RouterOS calls this menu /interface ovpn-client; on 6.47 to 7.9 it is
/interface openvpn client with the same properties. The username field is mandatory in RouterOS and we
set it to the site name — it is the certificate that authenticates the tunnel, which is why we do not
need your admin password for this. verify-server-certificate=yes makes the router check that it really
reached support.mikro.st and not somebody's laptop. The server answers on both address families
(194.14.217.97 and 2a03:f80:40:a18e::1), so a box on an IPv6-only uplink sets
protocol=udp6 and gets the same tunnel.
What that buys you
No port forwarding
Your router dials out, so it works behind CGNAT, behind the ISP's modem, and behind the double NAT you discovered when you tried to host something. No static public IP needed on your side, and it survives a dynamic address.
You keep the keys
The client certificate lives on your router and only on your router. We never see your Wi-Fi password, and if you use a read-only account we never see your admin password either. One certificate per site means one line to revoke.
Works on the cheap boxes too
OpenVPN is in Ubiquiti, DrayTek, Zyxel, ASUS, AVM and most TP-Link and NETGEAR firmware that has no WireGuard at all. Tenda is the exception, and for Tenda there is the dictation option below.
Same tunnel for monitoring
On the monitoring plan the tunnel stays up and we poll through it every 60 seconds. "You give us access? We make sure we keep it!" — that is the deal, in the other direction.
The two ways to authorise us
1. A support account on the router
The default, and what we recommend. You create a limited user, we log in through the tunnel with it, and nothing we do can lock you out of your own box.
/user group add name=support policy=read,test,ping
/user add name=mikro-support group=support password=<generated> \
comment="support.mikro.st"
# reach us only over the tunnel, never from the WAN:
/ip service set winbox address=10.44.9.0/24
/ip service set api address=10.44.9.0/24
Want us to be able to change things? Add ,reboot,write to the policy for the
duration of the visit and take it back afterwards. We will ask; we will not assume.
2. Full admin, temporarily
Faster for a one-off, and honest about what it is: we can see everything, including the Wi-Fi password and the VPN secrets. If you would rather not, use option 1 and stay on the phone for the two commands that need elevation.
| Policy | We can | We cannot |
|---|---|---|
| read,test,ping | see config, run tests, reach the internet for a download | change anything, reboot, save |
| +policy | manage other users' access | read secret values |
| full | everything, including the mistakes | nothing, we are careful |
Not MikroTik? Still fine
OpenVPN is old enough to be everywhere, so most non-MikroTik devices can build the same tunnel from their own web UI or config file. These are the paths we take, in the order we prefer them.
| Path | Works on | What we ask you to do | Cost |
|---|---|---|---|
| OpenVPN tunnel, router initiates | MikroTik 6.47+, Ubiquiti EdgeRouter and UniFi gateways, DrayTek Vigor, Zyxel USG/ATP, ASUS, AVM FRITZ!Box, GL.iNet, anything OpenWrt | Import the three files we send, or paste our .ovpn into the VPN page; newer TP-Link and NETGEAR models do OpenVPN client too |
included in a visit |
| Winbox or WebFig reached through the tunnel | MikroTik | Nothing after the tunnel exists; restrict the services to 10.44.9.0/24 as above |
included in a visit |
| You host the terminal, we dictate | Tenda, and older TP-Link, NETGEAR, D-Link units without a VPN client at all | Keep a chat or a phone call open while you paste what we ask for. Nine times out of ten this is enough | included in a visit |
| UniFi console or vendor cloud share | UniFi (site share), Ubiquiti, some TP-Link Deco | Share the site with ops@support.mikro.st, read-only |
no fee |
| Public IP + firewall protect | Anywhere with a real IPv4 address, when a tunnel is impossible | Allow our address 194.14.217.97 to reach the admin service; we bring the rest |
no fee |
Questions we get on the first mail
Does the tunnel slow down my internet?
No. Only our own traffic and a keepalive every twenty seconds ride through it; your users do not route across the tunnel at all, because we leave the default route alone. On a small board the AES-256-CBC data channel costs a few percent of one core while we are inside, and OpenVPN on RouterOS will use hardware acceleration where the chip has it.
Why OpenVPN and not WireGuard?
Because the point is reach: OpenVPN is in the firmware of nearly every device we are called about, it runs over UDP or TCP on a port an ISP will not interfere with, and a certificate per site is easier to hand over than a key exchange on a box whose UI you cannot read. Where a device does have WireGuard and no OpenVPN client — it happens — we use WireGuard; the tunnel is the thing, not the flavour.
My ISP blocks UDP. What then?
Rare, and OpenVPN has the answer built in: protocol=tcp on the same port, or move
the server to 443 for the sites that are really hostile. TCP-over-TCP is less pleasant under loss, which is why
we run UDP by default.
Can you see the rest of my network?
Only what we are told to. By default we reach the router's tunnel address and nothing else, which
is enough for 90 % of visits. To reach a switch or a camera we add one iroute for your certificate on
our side and you add a route back — two lines, and we send you both. And no other customer can see yours:
our tunnel server does not relay client-to-client traffic, so a site can only ever talk to us.
Who pays when the tunnel is the problem?
If we cannot get in because of the tunnel, and the tunnel is what we set up, we fix it for nothing. If the tunnel is fine and your firmware is 6.42, we tell you before we start spending minutes.
What happens when the certificate expires?
In practice: nothing, because it takes ten years to get there. The CA, the server certificate and
the certificate we issue your router are all signed for ten years — a support tunnel should not die because
of a calendar entry, and nobody should have to re-dial a working connection in 2033. We still watch the expiry
date and re-issue a new pair some months ahead, so the change is a quiet mail and two /certificate
import lines, not an outage you discover on a Saturday.
Do you need a static IP on my side?
No, and that is rather the point. The tunnel is initiated by you, so your address can change a dozen times a day and we still find each other.
When the tunnel is not the answer
A tunnel does not fix a device that cannot stay up long enough to be configured, and it does not do anything about the fibre modem in front of it. We have wasted enough visits on that to say it plainly:
- Router reboots every few minutes. Power supply first, config second. Hands needed.
- The ISP modem does the routing. Then the interesting device is not the one you bought, and the double NAT is a decision to make rather than a bug to fix.
- No OpenVPN client in the firmware. Most Tenda and older TP-Link units. We work through the UI with you, on the phone, same fee.
- No access at all. Lost admin password on a device with no recovery: a visit, or a reset and a rebuild, and the rebuild is often cheaper by mail.
Set the tunnel up with us
EUR 29
The certificate pair issued for your site, the client configured and tested from both sides, the closing command written down, and the whole thing documented in the same mail as the report. Free when you take a fix visit, because then it is already paid for.