Teltonika WANplex has officially launched, and it’s what I hoped it would be. Two weeks after it turned up as a single unexplained line in the RutOS 7.26.1 changelog, Teltonika has published a WANplex product page, a price list and a proper setup page in its wiki. WANplex is SD-WAN bonding built into RMS: your router splits traffic across up to four connections, and a hub you host yourself puts it back together. In this guide I’ll explain how it works, what it costs, how it compares with Bondix, and how to set up your own WANplex hub on a Linux VPS.
Earlier this week I wrote about what the RutOS 7.26.1 changelog hinted at and stuck my neck out with some guesses. Most of them have survived contact with reality, and I’ll mark my own homework further down.
The short answer: Teltonika WANplex is Teltonika’s own WAN bonding service, managed from RMS. It works on RUTX, RUTM and RUTC routers running RutOS 07.26.1 or newer, and bonds up to four interfaces per device (5G, 4G, Ethernet, Wi-Fi WAN or satellite) into one link. Licensing is one extra RMS credit per device, with no bandwidth tiers. A bonding-only credit costs €2.90 per 30 days, or €19 for a year. The catch, and for me the best bit, is that you run the hub yourself: Teltonika gives you an installer that runs in Docker on any Linux server, such as a VPS.
What Teltonika has launched
The launch email I received this morning pitches WANplex against the enterprise SD-WAN market, which it describes as expensive per-device subscriptions, bandwidth caps and multi-year contracts. Strip the marketing out and here’s what’s on offer:
- Teltonika’s own bonding. WANplex isn’t built on Bondix. It’s Teltonika’s own service, built into RutOS and RMS, and Bondix carries on as a separate option.
- Packet-level bonding. Teltonika says WANplex splits data streams at the packet level and sends them across every active link at once. If one link drops, traffic carries on over the others without dropping active sessions.
- Managed in RMS. You create the hub, add devices, pick which interfaces to bond and handle licensing all in the RMS platform many Teltonika users already have.
- Flat-rate credits. You pay the same whatever your throughput. There are no speed tiers.
- Primary and secondary servers. RMS lets you choose whether each device connects to a primary or secondary WANplex server, so you’re not stuck with a single point of failure.
- Self-hosted hub. RMS generates an installer for your hub, which you run on your own Linux machine. Teltonika isn’t in the data path.
Teltonika’s own examples are mobile command vehicles and first responders combining satellite and cellular, public transport and fleets keeping passenger Wi-Fi and live CCTV running, and branches and retail sites bonding fixed broadband with 5G to protect card payments, cloud systems and VoIP.
How Teltonika WANplex works
If you’ve read my Bondix and RUTM52 guide, the principle will be familiar. Failover waits for a link to die before switching. Load balancing spreads separate sessions across links, so one big upload still rides one SIM. Bonding uses every link for every session, which is why it needs something at the far end to put the traffic back together. In WANplex, that’s the hub.
The diagram shows the important point: there are two separate paths. RMS is the control plane. It’s where you create the hub, add devices and manage credits. Your actual traffic is split across the router’s links and reassembled by your WANplex hub. That’s exactly what I hoped for, because a bonding hub carries every byte a site sends, and I’d much rather that ran on a box I can see, size and pay for myself.
| Failover | Load balancing | WANplex bonding | |
|---|---|---|---|
| Links in use | One at a time | All, per session | All, per packet |
| One big upload or video stream | Uses one link | Uses one link | Uses every link |
| A link drops mid-session | Session reconnects on the backup | That session drops | Session carries on |
| Extra infrastructure | None | None | A WANplex hub on a server |
| Built into RutOS | Yes | Yes | Yes, from 07.26.1, configured in RMS |
Which routers support WANplex
According to Teltonika’s wiki, WANplex is currently supported only on RUTX, RUTM and RUTC family devices running firmware 07.26.1 or newer. That covers the routers I’d want for bonding: the RUTX12 and RUTX50 workhorses, the dual-modem RUTM range including the RUTM52, and the RUTC50. Each device can put up to four interfaces into the WANplex tunnel.
One thing worth remembering: the router does real work in bonding, splitting traffic and encrypting it into the tunnel. The faster the links you’re combining, the more the router’s CPU matters. Before you promise anyone a number, test the actual model you plan to deploy with the actual links.
WANplex pricing
This is where Teltonika is clearly aiming to cause a stir. Bonding is enabled with one additional RMS credit per device, on top of standard RMS Management. These are Teltonika’s published list prices in euros:
| Term | Bonding only (already on RMS) | RMS Management + Bonding bundle |
|---|---|---|
| 30-day credit | €2.90 | €5.80 |
| 1 year | €19 (€1.58 a month) | €33 (€2.75 a month) |
| 3 years | €28 (€0.78 a month) | €50 (€1.39 a month) |
| 5 years | €35 (€0.58 a month) | €60 (€1.00 a month) |
| 10 years | €47 (€0.39 a month) | €80 (€0.67 a month) |
The headline is the line Teltonika keeps repeating: no bandwidth tiers. Most bonding products I’ve priced over the years charge more as you go faster. Bondix licences, for example, are sold in throughput tiers; one European distributor lists IoT, Standard and Enterprise licences at up to 20, 75 and 200 Mbit/s. With WANplex, a site bonding two 5G modems pays the same as one bonding two 4G SIMs.
What the credit price doesn’t include is the hub server, the data on every SIM, and your time. Bonding uses every link at once, so expect data use across your SIMs to go up. Budget for that before you put four unlimited-looking SIMs into a box.
As a rough worked example, ten sites not yet on RMS, on the one-year bundle, come to 10 x €33 = €330 a year in licences, plus one hub server. For anyone used to managed bonded services, that’s a very different conversation, although you’re also taking on the job of running it. I set out where that trade-off sits in bonded 4G or a second router.
How my guesses held up
I promised I’d mark my own homework. Here’s what I predicted before launch, against what Teltonika has now published.
| My guess | What Teltonika published | Verdict |
|---|---|---|
| It’s bonding, not just failover | “SD-WAN bonding and failover”, packet-level aggregation | Right |
| It lives in RMS, under an SD-WAN banner | Configured in RMS, marketed as SD-WAN bonding | Right |
| You’ll still need a hub, and can run your own on a Linux VPS | RMS generates a hub installer that runs in Docker on any Linux distribution | Right, though the recommended spec isn’t exactly small |
| Hub resilience built in from day one | Devices can be pointed at a primary or secondary server | Right |
| Starts on RUTX and RUTC, RUTM next | RUTX, RUTM and RUTC from launch | Better than I guessed |
| Built on Bondix, or borrows from it | WANplex is Teltonika’s own service | Wrong |
Five out of six. The one I got wrong was Bondix: WANplex is Teltonika’s own, and Bondix carries on as a separate product. I’ll take five.
WANplex vs Bondix on Teltonika
For two years, if you wanted true bonding on a Teltonika router, Bondix was the answer, and it’s still a good one. WANplex isn’t built on it. It’s Teltonika’s own service, so you now have two separate ways to bond on the same hardware. Here’s how they compare today.
| Teltonika WANplex | Bondix on Teltonika | |
|---|---|---|
| Who makes it | Teltonika, built into RutOS and RMS | Bondix by SIMA, a third-party package |
| Where you manage it | RMS, alongside your existing fleet | Bondix package on the router, plus the Bondix server or cloud |
| Licensing | One RMS credit per device, flat rate, no bandwidth tiers | Licences sold in throughput tiers |
| Hub or server | Self-hosted hub, installer generated by RMS, runs in Docker | Self-hosted server image or Bondix-hosted service |
| Supported routers | RUTX, RUTM and RUTC on RutOS 07.26.1+ | A wide range of Teltonika models, installed from the Package Manager |
| Links per device | Up to 4 interfaces | Depends on licence and server package |
| Track record | Launched November 2026 | Years in the field, broadcast and events heritage |
My view: if your fleet is already on RMS and on supported routers, WANplex is now the obvious first thing to try, because the cost of finding out is one 30-day credit and a server. If you need bonding on older models, other hardware, or you want a fully hosted service, Bondix still has the edge. I’ll run both against the same links and write up the results.
Running a WANplex hub on a VPS
This is the part I’m most excited about. Teltonika’s wiki says the hub works on any Linux distribution, such as Debian, and needs only Docker, systemd and the standard networking tools. That means you can run it on a VPS in a UK data centre for a predictable monthly fee, rather than building a server room.
These are Teltonika’s documented requirements:
| Requirement | What Teltonika specifies |
|---|---|
| Operating system | Any Linux distribution, such as Debian |
| Packages | Docker (29.4.3 listed), systemd (247), and ss or netstat (iproute2 5.9.0 or net-tools 2.10-alpha) |
| Inbound port | UDP 40000 by default, or whichever port you set in RMS |
| Outbound port | TCP 15095 to RMS (18.196.62.30) |
| Recommended CPU | 4 cores / 8 threads |
| Recommended RAM | 16 GB |
| Network | At least a 1GbE NIC |
| Disk | At least 10 GB free |
Choosing a VPS
I run my own lab kit on LumaDock, and its line-up fits a WANplex hub well. It has a London location, so your hub sits close to UK mobile networks, offers Debian among its templates, includes DDoS protection, and lists its plans with unmetered bandwidth on a 1 Gbps network. That last point matters more than people expect. A bonding hub sends every byte from every site back out to the internet, and on the big cloud platforms that outbound traffic is billed. On a busy CCTV site, the egress bill can end up bigger than the server.
| LumaDock Ryzen plan | Dedicated vCPUs | RAM | NVMe | Listed price | Where I’d use it |
|---|---|---|---|---|---|
| R2 | 2 | 8 GB | 100 GB | $34.99 a month | Lab and trial hub, a handful of quiet sites |
| R3 | 4 | 16 GB | 200 GB | $69.99 a month | Production: the closest match to Teltonika’s recommendation |
| R4 | 8 | 32 GB | 400 GB | $127.99 a month | Larger fleets or busy video sites |
Prices are as listed on LumaDock’s site in November 2026, and longer billing terms are discounted, so check the current figure. Teltonika publishes a recommendation, not a minimum. I’ll start my own bench test on a smaller box and watch the CPU, but for anything a customer depends on I’d follow Teltonika’s recommendation and size up from there. If you’re running a secondary server, put it in a different data centre: LumaDock also has Frankfurt, Amsterdam and Paris.
Get a LumaDock VPS for your WANplex hub: London location, Debian, dedicated Ryzen cores and unmetered bandwidth on a 1 Gbps network.
WANplex setup: step by step
1. Get the routers ready
Update each router to RutOS 07.26.1 or newer and make sure it’s enrolled in RMS with a management licence. Decide which interfaces you’ll bond, up to four per device, and if they’re SIMs, put them on genuinely different mobile network groups. Two SIMs on the same network add bandwidth, but not much resilience.
2. Order the server
Order a VPS with Debian and a public IPv4 address. I’d use the LumaDock London location for UK sites. Add your SSH key at build time so you never need a password login.
3. Prepare the server
Log in, update the system and install Docker from Docker’s own repository, following Docker’s Debian install guide, which Teltonika links to. On Debian 12 that looks like this:
sudo apt update && sudo apt upgrade -y
sudo apt install -y ca-certificates curl iproute2
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/debian/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/debian $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt update
sudo apt install -y docker-ce docker-ce-cli containerd.io
docker --version
systemctl --versionThen lock it down. Allow SSH and the WANplex port, and nothing else inbound. Outbound is open by default, which covers the hub’s connection to RMS on TCP 15095.
sudo apt install -y ufw
sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow OpenSSH
sudo ufw allow 40000/udp
sudo ufw enable
sudo ufw status verboseWhile you’re there, turn off SSH password logins (PasswordAuthentication no in /etc/ssh/sshd_config) once you’ve confirmed your key works. Docker writes its own firewall rules, so after the hub is installed, check from outside which ports actually answer rather than trusting the ufw status alone.
4. Create the hub in RMS
In RMS, open WANplex and click + Add WANplex hub. Select the RMS company, give the hub a name and, optionally, a description. Under advanced options you can enter the IP address and port that devices should use to reach the hub, instead of the one RMS detects. Use this if the server sits behind NAT or you’ve chosen a port other than 40000. Then open the hub and download the server installer.
5. Install the hub
Copy the installer to the server, extract it and run it as a sudo user:
scp <hub-name>-install.tar.gz you@your-vps-ip:~
ssh you@your-vps-ip
tar xzvf <hub-name>-install.tar.gz
cd path/to/install/
chmod +x install.sh && sudo ./install.shThe script creates a systemd service at /etc/systemd/system/tlt-bonding_<hub-name>.service and starts it. The hub then connects to WANplex, and the RMS view changes to a logical map of your bonding server and any connected devices.
6. Add devices and switch it on
In the hub, click + ADD, select your RMS devices and click Proceed. Choose up to four interfaces per device for the tunnel, and the device appears in the hub’s list. From there you can enable or disable the tunnel per device, re-sync settings, choose primary or secondary server, see which interfaces are bonded, see the traffic each device has generated this session, and turn on credit auto-extend so a licence doesn’t quietly lapse.
Managing and troubleshooting the hub
The hub runs as an ordinary systemd service in a Docker container, so the usual tools apply:
# Service status
sudo systemctl status tlt-bonding_<hub-name>.service
# Stop and start
sudo systemctl stop tlt-bonding_<hub-name>.service
sudo systemctl start tlt-bonding_<hub-name>.service
# Is the container running?
sudo docker ps
# Hub logs, and follow them live
sudo docker logs tlt-bonding_<hub-name>
sudo docker logs tlt-bonding_<hub-name> -f
# Is the hub listening on its UDP port?
sudo ss -ulpn | grep 40000If a device won’t connect, my checklist is short. Is UDP 40000 open from the outside, at both the VPS firewall and any provider-level firewall? Does RMS have the right public IP and port for the hub? Can the server reach RMS on TCP 15095? Is the router on 07.26.1 or newer, with a valid WANplex licence? Nine times out of ten it’s the first one.
To remove a hub completely, Teltonika’s wiki gives the sequence: stop and disable the service, delete the unit file, reload systemd, delete /etc/bonding/hubs/<hub-name>, and remove the tlt-bonding-server Docker image.
Before you deploy it for a customer
I like this launch a lot. But bonding has caught people out before, so here’s what I’d check before it goes near a customer site:
- Test the “zero-drop” claim yourself. Pull a SIM mid-transfer, kill the Ethernet, drop the satellite. Run a single long TCP flow as well as a multi-stream test, and watch a live video call while you do it.
- Watch the hub’s CPU with every site live. One fast tunnel on the bench tells you very little.
htopon the hub during a busy afternoon tells you a lot. - Count the data. Every bonded link carries traffic all the time. Set usage alerts on every SIM.
- You’re running a server now. Patch it, back it up, monitor it, and use the secondary server option. A hub that goes down takes every bonded site with it.
- Diversity still matters. With three mobile network groups left in the UK, four SIMs is not four independent paths. Mix in fixed line or satellite where the site justifies it.
- Get the commercials in writing. Credit auto-extend is a useful switch. A lapsed licence on a site you forgot about is not.
Next up, I’ll build a hub on a LumaDock VPS, bond a RUTM52’s two 5G modems with a Starlink, and run it against Bondix on the same links. If WANplex delivers what Teltonika says at these prices, it changes the sums for a lot of UK sites that have been sitting on failover because bonding cost too much.
Quick answers
What is Teltonika WANplex?
Teltonika WANplex is Teltonika’s own SD-WAN bonding service, built into RutOS and managed from Teltonika RMS. It combines up to four internet connections per router, such as 5G, 4G, Ethernet, Wi-Fi WAN or satellite, into one link, splitting traffic at packet level and reassembling it at a hub you host yourself.
How much does WANplex cost?
Bonding needs one additional RMS credit per device on top of RMS Management. Teltonika lists bonding-only at €2.90 per 30 days, or €19 for 1 year, €28 for 3 years, €35 for 5 years and €47 for 10 years. An RMS Management plus bonding bundle starts at €5.80 per 30 days or €33 a year. There are no bandwidth tiers.
Which Teltonika routers support WANplex?
RUTX, RUTM and RUTC family routers running RutOS firmware 07.26.1 or newer, according to Teltonika’s wiki.
Do I need my own server for WANplex?
Yes. RMS generates an installer for a WANplex hub, which you run on your own Linux machine with Docker and systemd, such as a VPS. Devices can be pointed at a primary or secondary server.
What spec server does a WANplex hub need?
Teltonika recommends 4 CPU cores / 8 threads, 16 GB RAM, at least a 1GbE network interface and 10 GB of free disk space, running any Linux distribution such as Debian.
What ports does WANplex use?
The hub listens on UDP 40000 by default, or on the port you set in RMS. It also needs outbound TCP 15095 to communicate with RMS.
Is WANplex built on Bondix?
No. WANplex is Teltonika’s own bonding service, licensed through RMS credits with no bandwidth tiers. Bondix remains a separate third-party product for Teltonika routers, installed from the RutOS Package Manager and licensed in throughput tiers.
How many connections can WANplex bond?
Up to four interfaces per device can be included in the WANplex tunnel.
Sources: Teltonika Networks, WANplex SD-WAN bonding and failover product page and pricing, November 2026; Teltonika Networks WANplex launch email, 12 November 2026; Teltonika Networks Wiki, RMS WANplex, updated 11 November 2026; Teltonika Networks Wiki, RutOS 07.26.1 changelogs; Capestone, Bondix S.A.NE licence tiers; Docker, Install Docker Engine on Debian; LumaDock Ryzen VPS plans, checked November 2026. Prices are list prices at the time of writing and may change. The LumaDock links are referral links.



