Supported hardware
Qarvix connects devices in two ways, depending on the router's firmware. Devices on OpenWrt (today, every Teltonika line) get Qarvix's own agent - a small program that brings up a WireGuard tunnel and holds a persistent management channel with the controller. Devices on RouterOS (MikroTik) don't get an agent in the usual sense: instead, a RouterOS script is installed on the router that polls the controller itself and applies the configuration. The end result is the same for the user - a managed WireGuard tunnel and access from the dashboard - but the mechanism and the exact set of capabilities differ slightly between the two.
Devices
Choose a manufacturer to see its supported devices. The vendor list will keep growing.
| Line | Example models |
|---|---|
| RUT2M | RUT200, RUT241, RUT260 |
| RUT9M | RUT901, RUT906, RUT951, RUT956 |
| RUTM | RUTM08, RUTM09, RUTM10, RUTM11, RUTM16, RUTM20, RUTM30, RUTM50, RUTM51, RUTM52, RUTM54, RUTM55, RUTM56, RUTM59 |
| RUTX | RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1 |
| TRB1 | TRB140, TRB141, TRB142, TRB143, TRB145 |
| TRB2M | TRB236, TRB246, TRB247, TRB256 |
| Device | Status |
|---|---|
| RB2011 (RB2011UiAS-RM) | Verified on real hardware |
Teltonika is grouped by line rather than by specific model: devices in the same line share the manufacturer's SDK, so one agent build fits every model in that line at once. If your exact model isn't in the example but belongs to one of these lines, the agent for it already exists. The MikroTik list is shorter for now - today one device is officially confirmed, more on that below.
Every device listed above already gets:
- one-token connection through quick device onboarding;
- a managed WireGuard tunnel and a route to the LAN subnet behind the router;
- diagnostics and a device log in the Qarvix dashboard.
Beyond that, the feature set differs by vendor:
- Teltonika (OpenWrt) - a persistent management channel, over-the-air (OTA) agent updates with no site visit, remote access to the router's web interface and SSH over the tunnel.
- MikroTik (RouterOS) - instead of a persistent channel, a script polls the controller every 30 seconds and updates itself by checking a version hash; remote access is SSH only for now, web interface (WebUI) access over the tunnel isn't supported yet.
A lightweight agent for OpenWrt
The Qarvix agent for OpenWrt lines links only against libraries already present in RutOS firmware - libc, libuci, libubox, libopenssl3, and ca-bundle - and doesn't bring anything of its own. The built package weighs around 39-40 KB on MIPS-based lines (RUT2M, RUT9M, RUTM, TRB2M) and around 51 KB on ARM-based lines (RUTX, TRB1) - that's the weight of the whole package: the binary, the init script, and the config, not just the executable.
This matters especially for RUT2M, RUT9M, and TRB2M: these lines have just 16 MB of flash storage for the entire firmware, including the OS itself and the router's web interface. Agents built on heavier runtimes that bring their own dependencies typically weigh tens of megabytes - on a device with 16 MB of flash, there's simply no room for them.
How MikroTik gets its configuration
RouterOS doesn't let its own scripting language hold a persistent outbound WebSocket connection, so the usual C-agent doesn't fit here. Instead, a RouterOS script is installed on the router: once every 30 seconds it polls the controller and applies WireGuard, routes, and NAT rules itself through /interface wireguard, /ip route, and /ip firewall nat. A separate updater script checks a version hash every 5 minutes and pulls fixes automatically, with no reinstall and no site visit.
Because this is a script rather than a binary compiled for a specific processor architecture, the mechanism isn't tied to one model as tightly as the OpenWrt agent is. RB2011 is confirmed on real hardware today - if you have a different RouterOS device, get in touch and we'll help verify it.
Other devices on OpenWrt
The Qarvix agent is written in C and built for OpenWrt - this isn't a lock-in to Teltonika specifically, it's the platform all six lines above already run on. Thanks to that, the agent builds quickly for a new processor architecture, and support for a manufacturer you need gets added to the system without developing a new management protocol or reworking the dashboard.
If your client's hardware runs OpenWrt but isn't one of the currently supported lines, get in touch and tell us the model and manufacturer. We'll build and verify an agent for your device and add its manufacturer to the system - after that it becomes fully supported, on par with the Teltonika lines listed above. If the hardware runs RouterOS, see the MikroTik tab above - that's a different mechanism. The list of supported hardware will keep expanding.
How to check whether a model is supported
If a model belongs to one of the six Teltonika lines above, or it's a MikroTik RB2011, you can go straight to quick device onboarding. The install script detects the model on its own and doesn't require you to pick a build manually.
If, during installation, you get an error about an unsupported model or firmware, that means a build or script for that specific device doesn't exist yet. Diagnostics and common issues can help you tell this apart from a network or connection-token problem.
Related sections
- Quick device onboarding - how to install the agent on a supported model.
- Devices and VPN addresses - how a managed device differs from a static client.
- Diagnostics and common issues - what to check if a device won't connect.