WAN Bonding Becomes a Router App: Bondix Is the First Third-Party Software in the Teltonika Package Manager

For decades, a WAN bonding router was a purchase in its own right: a dedicated appliance, built solely to bond multiple internet lines, procured separately and operated separately from the rest of the site's network equipment. That assumption is now visibly shifting. Bondix Intelligence has placed its bonding package directly in the RutOS Package Manager on Teltonika's industrial routers – by its own account the first independent third-party application ever to be listed in the Package Manager's new third-party section (bondix.de/milestone). A WAN bonding router that once had to be procured as a standalone specialist device thereby becomes a package you install on router hardware you already own.

This article sets out what has actually changed in the installation process, why bonding is neither failover nor load balancing – the most common mix-up we see in our own advisory practice –, what Teltonika's own wiki says about supporting this third-party package, and for which routers and use cases WAN bonding genuinely pays off.

Until recently, installing third-party software on a Teltonika router was manual work: you had to download the matching .TAR.GZ package for your RutOS firmware from an external website, then upload it manually in the WebUI under Services → Package Manager → Upload. Every firmware update meant repeating the same process.

The third-party section in the RutOS Package Manager removes exactly this detour. Bondix itself names four concrete changes (bondix.de/milestone):

• No separate download from an external website
• No manual upload of installation files
• No reinstallation after RutOS firmware updates – Bondix updates itself automatically to the matching version
• An overall faster, simpler installation process

Instead of finding, downloading and uploading a file, the Package Manager now just needs: open Third-Party, select Bondix, install. Bondix describes the integration as available from RutOS 07.24 – neither Bondix nor Teltonika's own wiki states an explicit minimum version. We have already covered RutOS 07.24 itself in our overview of RutOS 7.24, 7.24.1 and 7.24.2.

This is the most common mix-up we see in Multi-WAN advisory conversations: failover, load balancing and bonding get used interchangeably, even though they are technically quite different – and RutOS already ships with the first two built in, no Bondix required.

Failover switches to a backup line if the primary line fails. Only one line is active at any given time; the second stands ready but carries no traffic during normal operation.

Load balancing distributes new sessions across several active lines. That increases the total usable capacity at a site, but each individual session stays bound to one of the lines. If that particular line fails, the session drops – load balancing doesn't protect the individual connection, it distributes load.

Bonding goes a step further: a single session uses several lines at the same time. The data stream is split across all available paths and reassembled at the far end. That adds up bandwidth per session and lets a live connection survive a line failure, because it never depends on just one line.

The practical difference for procurement: RutOS can do failover and load balancing out of the box, with no extra software – but not at the same time. Teltonika's own wiki explicitly states that load balancing and failover cannot run together (Teltonika wiki). With built-in tools alone, you therefore choose one or the other: resilience or load distribution. That either-or choice disappears with bonding, because a session runs across all lines regardless. Genuine bonding additionally needs the Bondix package on the router and a counterpart, the so-called bonding server, where the router reassembles the split data streams. Without that counterpart, you're still only looking at load balancing – the table below sets the three approaches side by side.

Something neither manufacturer newsletter mentions, but which matters for any procurement decision, is set out in Teltonika's own wiki on the Bondix installation (wiki.teltonika-networks.com/view/Bondix_by_SIMA): the page states explicitly that this is a third-party package – from Bondix Intelligence – not developed by Teltonika. By its own account, Teltonika takes no responsibility whatsoever for this package's compatibility, interoperability with other services, security or general stability.

That's not small print, it's a real purchasing and operational fact: anyone planning WAN bonding on a Teltonika router gets router hardware from one manufacturer and bonding software from another – with correspondingly separate responsibility if something doesn't work together in operation. Knowing this in advance lets you plan support and escalation paths properly, rather than improvising them once something breaks.

This is exactly where the supplier relationship matters. We supply Teltonika routers from our own stock and maintain a partnership with Bondix Intelligence alongside it – giving you a single point of contact for both sides of the installation, instead of having to coordinate two manufacturer support channels separately.

Teltonika's wiki lists the supported devices explicitly (wiki.teltonika-networks.com/view/Bondix_by_SIMA):

• the entire RUTX series
• the entire RUTM series
• RUT901, RUT906, RUT951, RUT956
• RUT200, RUT241, RUT260, RUT206, RUT271
• RUTC50

From our available range, these include the RUTX11, the RUTX50 and the RUT951 – all routers you might already be running for failover and load balancing, and which can be extended to genuine bonding with the Bondix package from the Package Manager, provided the matching counterpart is in place.

On its own project page, Bondix describes why temporary and mobile sites in particular have to manage without a reliable fixed-line connection: venues rarely offer business-grade internet access, so operators bring their own connectivity and often rely on unstable public or mobile networks. When point-of-sale systems, VoIP telephony, security cameras and guest Wi-Fi all run over a single mobile connection at once, ordinary mobile routers quickly reach their limits – and a dropped connection at the payment terminal means lost transactions and long queues (bondix.de/projects/retail-production).

Two case studies published by Bondix show what this looks like in practice:

• Festival deployment: a Teltonika RUTX11 router with Bondix bonded two LTE SIM cards from different network operators and served 50 point-of-sale systems running simultaneously. According to Bondix, this raised the transaction success rate to 99.99% – a figure Bondix itself gives for payment reliability in that specific project, not a general availability promise for the internet connection as a whole.
• Pop-up retail: for temporary retail spaces using a RUT360 router with Bondix, Bondix reports that set-up time per site fell from 2 hours to 20 minutes.

We've summarised what fundamentally distinguishes bonding from failover and load balancing in Multi-WAN bonding explained. Applied to typical use cases, that means: WAN bonding pays off wherever payment traffic depends on a single connection, wherever no fixed line is available on site, for temporary set-ups with tight commissioning windows, and anywhere video or VoIP sessions can't shrug off a line switch without disruption. For immediate bandwidth needs, load balancing is often already enough in many of these cases – but as soon as a single live session needs to survive a line failure, or needs more bandwidth than a single line can supply, there is no way around genuine bonding.

Moving from a dedicated bonding appliance to a router app in the Package Manager noticeably lowers the entry barrier – installation and updates now follow the same path as any other router maintenance. That doesn't change two things you should clarify before procurement, though: first, that genuine bonding needs a counterpart in addition to the router package, and second, that Teltonika explicitly takes no responsibility for this third-party package.

If you'd like to work out whether failover, load balancing or genuine bonding is the right choice for your site, which router from our available range fits, and how the counterpart is operated, get in touch. You can read more about how router, bonding and data plan work together in Router, bonding, data plan: the three building blocks of a resilient connection.

This article was researched and written with AI assistance and reviewed by Ascend before publication.