Bondix Wiki - User contributions [en]

Downloads

2026-07-15T13:13:40Z

Sylvia:

= Teltonika RutOS 07.24 =

In Teltonika's RutOS Version 07.24, published July 8, 2026, Bondix is listed as the '''first Third-Party app''' in Teltonika's Package Manager.

This means two things:
# Once you update to RutOS 07.24, you need no longer '''install Bondix manually''' in the absolutely matching versions!
# All your previous Bondix settings are kept for your devices - with the only exception of Teltonika ALTOS Routers.

= Bondix Software Downloads =

This page provides download links for Bondix software compatible with various devices and firmware versions. Select the appropriate file based on your device model and firmware version.

'''Current Release Version:''' 1.26.01.x''' '''
{{Colored_box|Text=By initiating the download of the software from this site, you hereby acknowledge and consent to be bound by the terms of our [https://www.bondixintelligence.com/_files/ugd/226d8a_e5e6dbbc57124ed985bad80fa49ccbc8.pdf End User License Agreement (EULA)] and Terms of Use, which constitute a legally binding contract between you and SIMA GmbH.

Please review these documents carefully prior to downloading.}}

==Client==

{{Colored_box|Text='''ONLY APPLICABLE PRE-RutOS 07.24:''' Please make sure to '''EXACTLY match your RUTOS''' version when downloading your Bondix client.

Example: If your router is updated to 07.22.1, our Bondix version 1.26.01.2/07.22 is '''NOT the correct version''' and you need to '''DOWNGRADE''' your router to 07.22 to be able to use Bondix.}}

===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!1.25.7.6/07.20.3 (Prev)
!1.26.01.3/07.22.3 (Stable)
!1.26.01.3/07.23.5 (Latest)
|-

|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTX_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTX_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTX_R_00.07.23.5.tar.gz Download]
|-
|RUTM
|RUTM09, RUTM10, RUTM11, RUTM16, RUTM20, RUTM30, RUTM31, RUTM50, RUTM51, RUTM52, RUTM54, RUTM55, RUTM56, RUTM59
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTM_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTM_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTM_R_00.07.23.5.tar.gz Download]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956, RUT976, RUT981, RUT986
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT9M_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT9M_R_00.07.23.5.tar.gz Download]
|-
|RUT2M
|RUT200, RUT202, RUT204, RUT206, RUT241, RUT260, RUT271, RUT276, RUT281
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT2M_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT2M_R_00.07.23.5.tar.gz Download]
|-
|RUTC
|RUTC40, RUTC41, RUTC42, RUTC50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTC_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTC_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTC_R_00.07.23.5.tar.gz Download]
|-
|RUTE
|RUT206, RUT271
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTE_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTE_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTE_R_00.07.23.5.tar.gz Download]
|-
|OTD5
|OTD500
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-OTD5_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-OTD5_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-OTD5_R_00.07.23.5.tar.gz Download]
|-
|ATRM50
|ATRM50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-ATRM50_R_00.07.20.3.tar.gz Download]
|-
|ALTOS
|ALTOS
|colspan="3"| Coming soon
|}

====EOL====
For routers designated as [https://teltonika-networks.com/support/eol-products "End of Production"] by Teltonika Networks, we no longer provide updated Bondix Client versions. If your device is marked as EOL and you require further support or newer versions, please contact us directly via email.

==Server==

===Latest Version (1.26.01.2)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.26.01.2.sh install-bondix-server-1.26.01.2.sh]

===Stable Version (1.25.7.6)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.25.7.6.sh install-bondix-server-1.25.7.6.sh]

Proceed to [[Manuals/Server| Installing a Bondix Server]].

[[Category:General]]

Server Configuration

2026-06-11T11:43:17Z

Sylvia:

[[Category:General]]
== Server Commands ==
{| class="wikitable"
|-
|
=== add-apikey ===
Adds an authentication key to use with the [[Server HTTP Api | HTTP API]].
{| class="wikitable"
|+Parameters
|-
|key||A secret string used to authenticate an API request.
|}
| style="width: 40%" |
<nowiki>{
"target": "server",
"action": "add-apikey",
"key": "a-secret-key"
}</nowiki>
|-
|
=== add-environment===
Adds an environment. Deprecated, you can directly create environments in the web interface instead.
{| class="wikitable"
|+Parameters
|-
|settings||Object with JSON settings for this environment
|-
|name
|Name used for the environment
|}
| style="width: 40%" |
{
"target": "server",
"action": "add-environment",
"name": "env123",
"settings": {
"tunnelNetwork": "169.254.19.1/24",
"udpListenerHost": "0.0.0.0",
"udpListenerPort": "44343",
"disableTunnelToTunnelTraffic": true
}
}
|-
|
=== add-http ===
Adds an unencrypted http listener for web interface access.
{| class="wikitable"
|+Parameters
|-
|host||Host/IP to be used to for the listener. Use 0.0.0.0 to bind on all interfaces.
|-
|port
|Port used for the listener. Defaults to 80
|}
| style="width: 40%" |
{
"target": "server",
"action": "add-http",
"host": "0.0.0.0",
"port": "80"
}
|-
|
=== add-https ===
Adds an encrypted https listener for incoming tunnel connections and web interface access.
{| class="wikitable"
|+Parameters
|-
|host||Host/IP to be used to for the listener. Use 0.0.0.0 to bind on all interfaces.
|-
|port
|Port used for the listener. Defaults to 443
|-
|cert
|Certificate file to use in PEM format. If none is supplied, a self signed certificate will be used instead.
|-
|key
|Certifikate key to use in PEM format. If none is supplied, a self signed certificate key will be used instead.
|-
|rootCA
|Specifies a root CA file that should be used in order to authenticate client tunnels using certificates.
|-
|allowTunnel
|Specifies whether to accept incoming tunnel connections.
|-
|allowMonitor
|Specifies whether to enable the web interface on this port.
|}
| style="width: 40%" |
{
"target": "server",
"action": "add-https",
"host": "0.0.0.0",
"port": "443",
"allowMonitor": true
}
|-
|
=== add-user ===
Adds an user/password pair that can be used to log into the server's web interface.
{| class="wikitable"
|+Parameters
|-
|user||The username
|-
|password
|The password
|}
| style="width: 40%" |
<nowiki>{
"target": "server",
"action": "add-user",
"user": "admin",
"password": "bad password"
}</nowiki>
|-

|
=== set-fallback-watchdog ===
Using this command, the server acts as a backup instance. When tunnels are connected, it will probe the specified url in regular intervals. If the probe succeeds, connected tunnels are instructed to connect to the primary server.
{| class="wikitable"
|+Parameters
|-
|url||The url used for probing the primary server.
|-
|interval
|The interval in seconds that should be probed
|-
|maxTunnel
|Amount of tunnels that should be disconnected in one go. This is useful to prevent many tunnels reconnecting at the same time to the primary server, causing unintended load spikes.
|}
| style="width: 40%" |
{
"target": "server",
"action": "set-fallback-watchdog",
"url": "https://10.1.2.3/api/v1/ping",
"interval": 3000,
"maxTunnel": 10
}
|-

|
=== slow-shutdown ===
Starts slow shutdown. This will disconnect all tunnels individually and tell them to connect to a different (backup) server.
{| class="wikitable"
|+Parameters
|-
| ||
|}
| style="width: 40%" |
{
"target": "server",
"action": "slow-shutdown"
}
|-

|
=== set-password-authentication ===
Sets a global flag enabling or disabling password based authentication. When disabled, only certificate authentication is possible.
{| class="wikitable"
|+Parameters
|-
|enabled||true or false
|}
| style="width: 40%" |
{
"target": "server",
"action": "set-password-authentication",
"enabled": true
}
|}

==System Commands==
{| class="wikitable"
|-
|
===shutdown===
Shuts down the client and terminates.
| style="width: 40%" |
<nowiki>{
"target": "system",
"action": "shutdown"
}</nowiki>
|-

|
===set-log===
Enables logging to file or changes output file.
{| class="wikitable"
|+Parameters
|-
|file||The filename that the log should be written to. Required.
|-
|fileMode||can be <code>append</code> or <code>overwrite</code>. Required.
|}
||
<nowiki>{
"target": "system",
"action": "set-log",
"file": "/var/log/saneclient.log",
"fileMode": "append"
}</nowiki>
|-
|
===set-script-path===
Changes the directory that points towards the client scripts. (/opt/bondix/client/scripts by default)
{| class="wikitable"
|+Parameters
|-
|path||Path to the new bondix script directory.
|}
||
<nowiki>{
"target": "system",
"action": "set-script-path",
"path": "/etc/bondix/scripts"
}</nowiki>
|-
|
===set-webinterface===
Enables the integrated webserver & debug webinterface.
{| class="wikitable"
|+Parameters
|-
|host||IP that the service should listen on. Required.
|-
|port||TCP Port that the service should listen on. Required.
|-
|allowConfig||En- or disables web configuration. Not required, enabled by default.
|-
|allowMonitor||En- or disables web monitor. Not required, enabled by default.
|-
|configApiKey||The password required to access configuration & monitor. Not required, "123456" by default.
|-
|webroot||Web root directory. Points to the "www" subdirectory in installation directory. Not required, changing not advised.
|}
||
<nowiki>{
"target": "system",
"action": "set-webinterface",
"host": "0.0.0.0",
"port": "80",
"allowConfig": false,
"allowMonitor": true,
"configApiKey": "123456",
"webroot": "/tmp/"
}</nowiki>
|}

Server Certificates with LetsEncrypt

2026-06-11T11:43:07Z

Sylvia:

[[Category:General]]
[[Category:SSL]]
== Set up Bondix Server with LetsEncrypt ==
To use a LetsEncrypt certificate with Bondix, you'll first need a (sub)domain that points towards your server's IP.

First, make sure that LetsEncrypt certbot is installed. To do this on Ubuntu or other debian based systems, do this:
sudo apt install certbot
Afterwards, run certbot with the argument "certonly". Cerbot will ask you how it should authenticate, and we are going to select the method of using a temporary webserver ("standalone"). There are a few follow-up questions that need to be answered, until it will eventually ask for the domain name that you would like a certificate for:
~# certbot certonly
Saving debug log to /var/log/letsencrypt/letsencrypt.log

How would you like to authenticate with the ACME CA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Spin up a temporary webserver (standalone)
2: Place files in webroot directory (webroot)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): '''1'''
Enter email address (used for urgent renewal and security notices)
(Enter 'c' to cancel): '''your@email.here'''

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please read the Terms of Service at
<nowiki>https://letsencrypt.org/documents/LE-SA-v1.3-September-21-2022.pdf</nowiki>. You must
agree in order to register with the ACME server. Do you agree?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: '''y'''

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you be willing, once your first certificate is successfully issued, to
share your email address with the Electronic Frontier Foundation, a founding
partner of the Let's Encrypt project and the non-profit organization that
develops Certbot? We'd like to send you email about our work encrypting the web,
EFF news, campaigns, and ways to support digital freedom.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: '''n'''
Account registered.
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): '''your.domain.name'''
Requesting a certificate for ''your.domain.name''

Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/''your.domain.name''/fullchain.pem
Key is saved at: /etc/letsencrypt/live/''your.domain.name''/privkey.pem
This certificate expires on ''20xx-xx-xx''.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If you like Certbot, please consider supporting our work by:
* Donating to ISRG / Let's Encrypt: <nowiki>https://letsencrypt.org/donate</nowiki>
* Donating to EFF: <nowiki>https://eff.org/donate-le</nowiki>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Parts that need your user interaction is in '''bold''', while text that will differ in your scenario is in ''italics'')

We now have a certificate and keyfile. In order to tell Bondix server to use these certificates, we must edit the file /etc/bondixserver.json

In that file, we are looking for a line that looks like this:
{"target": "server", "action": "add-https", "host": "0.0.0.0", "port": "443", "allowMonitor": true},
We will extend this line to point towards the certificate & keyfile, like this:
{"target": "server", "action": "add-https", "host": "0.0.0.0", "port": "443", "allowMonitor": true,
"cert": "/etc/letsencrypt/live/''your.domain.name''/fullchain.pem",
"key": "/etc/letsencrypt/live/''your.domain.name''/privkey.pem"},
Make sure that you are using valid JSON. Finally, restart the server via:
sudo systemctl restart bondix
Finally, test that you can reach your server under <nowiki>https://your.domain.name</nowiki>

'''(Please note, that after every renewal of the certificate a restart of the Bondix service will be required.)'''

Server/Routes

2026-06-11T11:42:58Z

Sylvia:

[[Category:General]]
[[File:Routes Settings.png|thumb]]

== Bondix Server Routes ==
With version 20230311 and newer, client and server routes are now accessible in the server's tunnel settings.

Client routes are routes that are applied on the client (most commonly a default route to route all traffic), while server routes are applied on the server, pointing towards a specific tunnel. By default, server routes are not required as all traffic is masqueraded by the client. All routes must be in proper CIDR notation.

On the client, we use 0.0.0.0/1 and 128.0.0.0/1 instead of a normal default route, as this reduces potential issues with pre-existing WAN default routes.

=== bxutil Usage ===
Server routes can also be dynamically set up using the command line util "bxutil"

Add a server route:
# ./bxutil route <TUNNEL> add <NETWORK>
Remove a server route:
# ./bxutil route <TUNNEL> del <NETWORK>
Remove all routes:
# ./bxutil route <TUNNEL> clear
<TUNNEL> must be a valid tunnel name, <NETWORK> a valid network in CIDR notation (e.g. 192.168.0.0/24).

=== Dynamic Routing Example ===
In the following example, we'll use some recent additions to dynamically set up a client-given server route when a tunnel connects. Note that this example is not suitable for real-world applications as it trusts arbitrary input data from a remote client to create routes, which can have potentially harmful consequences. Version 20230311 or newer required.

==== Client Prerequisites ====
We'll extend our saneclient.json to include a meta tag containing our desired network route. This is done using the command set-meta.
<nowiki>{"target": "tunnel", "action": "set-meta", "info": {"network": "192.168.172.0/30"}}</nowiki>
If you are using pre-generated saneclient.json (e.g. on Teltonika devices), we'll have to get back to you on how to achieve this. You'll have to find out yourself at this point, sorry!

==== Server Prerequisites ====
We create the directories & script files "/opt/bondix/server/scripts/tunnel-connect.d/10-addroute.sh" and "/opt/bondix/server/scripts/tunnel-disconnect.d/10-removeroute.sh" and make them executable via chmod a+x <file>.

===== Contents of 10-addroute.sh: =====
#!/bin/sh
TUNNEL="$1"
NET=`/home/bondix/server/bxutil get-meta "$TUNNEL" network`
if [ "$NET"E!= "null" ]; then
/home/bondix/server/bxutil route "$TUNNEL" add "$NET"
fi
When a tunnel connects, bxutil returns the "network" meta information for the target tunnel. If it exists, the server route is created.

===== Contents of 10-removeroute.sh: =====
#!/bin/sh
TUNNEL="$1"
NET=`/home/bondix/server/bxutil get-meta "$TUNNEL" network`
if [ "$NET"E!= "null" ]; then
/home/bondix/server/bxutil route "$TUNNEL" del "$NET"
fi
When a tunnel disconnects, we remove the server route.

When done correctly, we should now see the server route being added when the tunnel connects.That's it!

Server/Configuration

2026-06-11T11:42:47Z

Sylvia:

[[Category:General]]
== Server Configuration ==
By default, the server configuration in <code>/etc/bondixserver.json</code> allows to set up many things via the web interface - environments and tunnels that are created dynamically (via the web interface) are stored in /etc/bondix/.

However, you can customize Bondix server to adjust your requirements, such as:

* Have the web interface only accessible on a dedicated IP/port
* Disable the webinterface completely
* Set up tunnels statically

=== Configuration Layout for /etc/bondixserver.json ===
Configuration is stored in JSON, as an array of configuration commands. Lets inspect the default configuration:

<pre>
[
{"target": "tunnel", "action": "set-settings-location", "directory": "/etc/bondix/"},
{"target": "server", "action": "add-https", "host": "0.0.0.0", "port": "443", "allowMonitor": true},
{"target": "server", "action": "add-http", "host": "0.0.0.0", "port": "80", "allowMonitor": true},
{"target": "server", "action": "add-user", "user": "admin", "password": "password"},
{"target": "server", "action": "set-web-login", "password": "password"}
]
</pre>

Server/Changing Ports

2026-06-11T11:42:36Z

Sylvia:

[[Category:General]]
The Bondix server typically uses TCP port 443 for its web interface and to handle incoming tunnel connections, employing TCP for control messages and UDP for data transport. To modify these port settings or segregate them for enhanced security and restricted access to the server's web interface, follow this guide to adjust the default TCP port configuration.

== Modifying the TCP Port Configuration ==

TCP port settings are located in ''/etc/bondixserver.json'' (or ''/etc/saneserver.json'' for older installations), formatted in JSON. Avoid syntax errors in this file to prevent the server daemon from failing to start. The default configuration sets up a TCP listener as follows:

<pre>
{"target": "server", "action": "add-https", "host": "0.0.0.0", "port": "443", "allowMonitor": true},
</pre>

This configuration listens on any IPv4 address on port 443, with "allowMonitor" enabled for web interface access.

== Differentiating Web Interface and Incoming Tunnels ==

Replace the default command with two distinct commands to separate the web interface from incoming tunnel connections:

<pre>
{"target": "server", "action": "add-https", "host": "10.10.0.1", "port": "443", "allowMonitor": true, "allowTunnel": false},
{"target": "server", "action": "add-https", "host": "1.2.3.4", "port": "44343", "allowMonitor": false},
</pre>

The first command configures a listener on a private network IP with web interface access only, and the second sets up a listener for incoming tunnel connections on a custom port, rejecting other requests with HTTP 405 errors.

== Ensuring Configuration Validity and Server Restart ==

Verify the JSON syntax of ''/etc/bondixserver.json'' before restarting the server. Use `json_pp` for syntax verification.
<pre>
cat /etc/bondixserver.json | json_pp
</pre>

Restart the Bondix server with:
<pre>
sudo systemctl restart bondix
</pre>

== Client Configuration for Non-standard Ports ==
[[File:Bondix Client Custom Port.png|thumb|Entering a endpoint server IP using custom TCP port 44343]]

For a custom port, specify this port in the client's server string, appending the port number after the IP address, separated by a colon.

Server/Access Control

2026-06-11T11:42:25Z

Sylvia:

[[Category:General]]
Bondix Server 20230619 introduces access control settings for its webinterface. When creating a user in /etc/bondixserver.json, the following properties can now be populated:
{"target": "server", "action": "add-user",
"user": "xxx", "password": "xxx",
"write": true, "read": true,
"allowedSections": [], "blockedSections": [],
"allowedEnvironments": [], "blockedEnvironments": [],
"allowedTunnel": [], "blockedTunnel": [],
"allowedFunctions": {}, "blockedFunctions": {}
}
The new parameters are optional. In essence, there are both '''whitelists''' and '''blacklists''' for access to webinterface sections, tunnels, environments and functions.

If a whitelist is empty, access is always permitted, otherwise only items in the whitelist (and not on the blacklist) accessible.

When "read" or "write" is set, general reading and writing capabilities are set (to e.g. create users with read-only access).Otherwise, a function access list can be created for custom access.

=== Sections ===
The following sections are available:

* status (aka Overview page)
** get (read) -> returns status overview page details
* environment
** get (read) -> get environment settings
** set (write) -> set environment settings
** create (write) -> creates a new environment
** delete (write) -> removes an environment
** create-tunnel (write) -> creates a new tunnel
** reset-tunnel (write) -> resets/reconnects a tunnel
** reset-channel (write) -> resets/reconnects a tunnel channel
** delete-tunnel (write) -> removes a tunnel
** list (read) -> returns a list of environments
** get-tunnel (read)
** set-tunnel (write)
* tunnel
** disconnect-all (write) -> disconnect all tunnels
** create (write) -> creates a new tunnel
** reset (write) -> resets/reconnects a tunnel
** reset-channel (write) -> resets/reconnects a tunnel channel
** get (read) -> gets tunnel information & settings
** set (write) -> updates tunnel settings
** delete (write) -> removes a tunnel
* license
** scan (write) -> starts scanning for license files (offline)
** rename (write) -> renames the current instance (online)
** changelicense (write) -> change license type (online)
** activate (write) -> activate a new license (online)
** get (read) -> return detailed license information
* log
** get (read) -> get log lines

Example: User can only access the "env0" environment, cannot add/delete or modify environments, or access the license page.
{"target": "server", "action": "add-user", "user": "me", "password": "honk",
<nowiki> </nowiki>"allowedEnvironments": ["env0"], "blockedFunctions": { "environment": ["set", "create", "delete"]}}}

==== Remarks ====

* When an environment is renamed, access control will no longer match to it's specified name.
* there is an overlap of functions in environments & tunnels (create-tunnel etc). They are redundant.
* Environment read access is required to access its tunnels.

Main Page

2026-06-11T11:42:14Z

Sylvia:

[[Category:General]]
{{DISPLAYTITLE:Start}}

== Welcome! ==

This is the Bondix Wiki, our ever-growing knowledge base. Here, we collect all things Bondix. We offer handy quick-start information but also in-depth how-tos for installation, debugging, and general understanding, as well as pretty-looking and informative marketing material.

Feel free to roam around and take all the wisdom you need to bring your Bondix knowledge and understanding to the next level.

== Get Started ==

This section helps you get your Bondix system up and running in no time.

=== Bondix Hosted Essential ===

#[[Howto essential|Bondix Hosted Essential How-To]] Setup Bondix Hosted Essential on your Teltonika device.

=== Classic Bondix Installation ===
# <big>'''[[Downloads|Download the latest release versions]]'''</big> Download the latest Bondix software suitable for your device and see changelogs and release notes. Download & installation are free-of-charge for all of our software.
# [[Client Installation|Bondix Client Installation]] Install Bondix on your Teltonika device.
# [[Server|Bondix Server Installation]] Install and configure your Bondix server.

{{Colored_box|Text=Bondix Licenses have a fixed start and end date and cannot be renewed. If they expire, you need to purchase a new Bondix license code and insert it into your server the same way you did the first time: [[Server|Bondix Server Installation]]!}}

=== Bondix CloudLink Bundle ===

If you want to get your '''Bondix CloudLink Bundle''' up and running, our partner [https://www.unwirednetworks.com Unwired Networks] has a detailed step-by-step manual for that: [https://docs.unwirednetworks.com/docs/cloudlink/teltonika_cloudlink.html Bondix CloudLink]

{{Colored_box|Text=If you need technical assistance, please open up a support ticket in our [https://support.bondix.net/ Bondix Support Portal]!}}
=== Manuals ===
In our manuals, you can find more detailed information on different settings and values that can cater to special circumstances, environments, and needs. They are updated continually, so screenshots may vary. The overall system is the same.
* [[Manuals/Client|Bondix on Teltonika devices]]
** [[Client Installation]]
** [[General Teltonika Router Settings]]
** [[Configuration Mode]]
** [[Tunnel Preset]]
** [[Interfaces]]
** [[Advanced Settings]]
** [[Layer 2]]
** [[Monitor 7.02.x]]
** [[Status]]
* [[Manuals/Server|Bondix Server Setup]]
** [https://docs.unwirednetworks.com/docs/cloudlink/teltonika_cloudlink.html Bondix CloudLink]
** [[my.bondix.cloud]]
* [[Manuals/Webshop|How to order Bondix in the Bondix Webshop]]

== General Information ==
This section gives you information on what Bondix is and how it works. Also, it's where we collect FAQs and especially their answers.
* [[Architecture]]
* [[Licenses]]
* [[FAQs]]

== Deep-dive Topics ==
In this section, you'll find specialized knowledge that is very technical and/or serves as a how-to for special use cases.
=== Client and Server ===
* [[Transparent Bonding Proxy]]
* [[Teltonika Portforwarding|General port forwarding]]
* [[Quality of Service]]
* [[Layer2]]
* [[Presets]]
* [[QuickConnect]]
* [[DMZ and 1:1 NAT configuration]]

=== Client ===
* [[Client/StaticRoutes|How to create static routes]]
* [[Teltonika Portforwarding|How to create a port-forward with Teltonika Routers]]
* [[Starlink|Bondix and Starlink]]
* [[Client]]
* [[Client/OpenWRT]]
* [[Client/RUTX12]]
* [[Client Configuration]]

=== Server ===
* [[Certificates|How to setup certificate-based authorization]]
* [[Server Capacity|How to calculate how many Bondix Servers you need]]
* [[Server Licensing|How to add licenses to your Bondix Server]]
* [[Server/Access Control]]
* [[Server/Changing Ports]]
* [[Server/Configuration]]
* [[Server/Routes]]
* [[Server Certificates with LetsEncrypt]]
* [[Server Configuration]]

== Marketing Material ==
Here, you can find all marketing material we have to share in one place.

===== Basic Product Info =====
[[File:Bondix-product-info-2024.pdf|thumb]]
[[File:Bondix-product-info-2024-de.pdf|thumb]]

Product images
<gallery>
Bondix-product-license-trial-web.png|Product image Trial license
Bondix-product-license-iot-web.png|Product image IoT license
Bondix-product-license-standard-web.png|Product image Standard license
Bondix-product-license-enterprise-web.png|Product image Enterprise license
Bondix-product-license-ultimate-web.png|Product image Ultimate license
</gallery>

===== Presentations =====
'''Generic'''

[[File:Presentation-bondix-wan-bonding-generic-202308.pdf|thumb|What is WAN Bonding?]] 
[[File:Presentation-bondix-licensing-202309.pdf|thumb|Bondix licensing in a tiny nutshell]]

'''Teltonika-specific'''

[[File:Bondix-webinar-dec2022-web2.pdf|thumb|Joint webinar Bondix and Teltonika, Dec 2022]] -->
[https://youtu.be/GSKhc_qOp1o YouTube - Paving New Bonding Possibilities in IIoT]

Server Licensing

2026-06-11T11:41:55Z

Sylvia:

[[Category:General]]
== First-time license activation ==
If you need to license your first Bondix Server, you need to activate the Bondix Server Tunnel license under the menu item “Licensing”.

<gallery widths="500" heights="300" perrow="2">
File:4-nolicense.png
File:5-activate-license.png
</gallery>

Enter the Bondix license key here, as well as a valid email address to which the license key is bound. You can also enter a name for the server instance here. Then press “Submit”.

<gallery widths="300" heights="200">
File:6-license-key.png
</gallery>

After the successful activation, the Licensing overview will display the number of licensed tunnels as well as the expiry date of your active tunnel subscriptions with the respective expiry date and the maximum number of active server instances possible under this license number.

<gallery widths="550" heights="400">
File:Bondix-123101-licensing.png
</gallery>

== Changing licenses ==

=== Adding more tunnel licenses ===
You can add further additional tunnel/server instances at any time under the item “Activate License”. Just enter the license code and click "Submit".

=== Changing Server Throughput profiles (Instances) ===
With Bondix, an instance is a Bondix server installation. This server installation shows all active tunnels with the number of instances they can be installed on and the date they expire. An instance can be adjusted to serve only '''ONE(!)''' type of throughput / tunnel bandwidth. So, if you have 3 different types of license, e.g. 20 Mbps, 100 Mbps and 200 Mbps, you need 3 different instances - which is no problem as any Bondix license allows you to license at least two different instances for one active tunnel. However, it is vital that you register all Bondix server instances you want to manage to ONE email address, otherwise you won't be able to change instances.

If you want to change an instance and thus the licenses bound to it to a new type of tunnel bandwidth, make sure that you are logged in with the correct email address, scroll down to "Change Instance", enter the name of the instance, and choose the desired tunnel bandwidth. You will only see option that are within the maximum throughput for the licenses you purchased. Then, click "Submit".

Server Capacity

2026-06-11T11:41:45Z

Sylvia:

[[Category:General]]
== Guidelines on calculating Bondix server capacity ==

For simplicity, we'll look at an example that calculates with 10 Mbps 24/7 and a 1 Gbps uplink without congestion.

=== Clock speed ===

10 active Tunnels require 1GHZ CPU clock speed (x86 Intel Xeon or AMD Epyc 2nd gen processors) which means 100 users/10 tunnels require 10 GHZ CPU core clock speed.

So if your server has cores with CPU clock speeds of 2 GHZ per core, each of the cores could handle 20 tunnels/devices and you would need at least 5 cores to handle 100 tunnels + 1 additional core for the server itself.

=== RAM ===

Bondix needs 200 MB of RAM per environment on the server, so if you distribute your tunnels between 4 environments on the server (25 per environment), the server will use 800 MB of RAM for the environments and another 200 MB for general server functions.

So the total here is at least 1 GB.

=== RAM for Bonding ===

To be able to bond, Bondix server needs 50 MB per tunnel. So in this example, 100 tunnels will require 5 GB of RAM on the server.

This means in effect:

<nowiki>To terminate 100 tunnels with an average load of 10 Mbps per tunnel 24/7, we need
- 6 cores of at least 2 GHZ Clock speed per core
- 6 GB of RAM
- 1 Gbps Server uplink</nowiki>

If your customers only need 5 Mbps or less, the same server will be able to terminate around 200 tunnels if RAM is increased to 12 GB since we need 50 MB per tunnel on the server side.

Certificates

2026-06-11T11:41:36Z

Sylvia:

[[Category:General]]

= Certificate-Based Authentication =
Bondix offers the capability to authenticate incoming tunnel connections using certificates. This method eliminates the need for manual tunnel creation for each device on the server. By creating a root certificate and signing client certificates with it, the server can automatically generate ad-hoc tunnel configurations for incoming connections, enhancing scalability.

For guidance on configuring the SSL certificate on your Bondix server, please refer to: [[Server_Certificates_with_LetsEncrypt|Server Certificates]].

== Prerequisites ==

=== Setting Up Certificates ===
The Bondix server includes scripts within the ./ssl subdirectory for certificate setup:

cd /opt/bondix/server/ssl
./create-server-cert.sh
This script generates a self-signed server certificate and a root certificate for client certificate signing. It is executed automatically post-installation. Ensure the presence of <code>client-root.key</code> and <code>client-root.crt</code> in the ./ssl subdirectory; if absent, rerun the script.

Apply this parameter where necessary, considering multiple listeners or separate ports for different services. Note that adding this authentication method has no effect where incoming tunnels are not allowed. Restart the server with <code>systemctl restart bondix</code> to apply changes.

=== Generating a Client Certificate ===
Generate client certificates using a script located in the ssl server subfolder:
cd /opt/bondix/server/ssl
./create-client-cert.sh <TunnelName>

Ensure the script is executed in the intended directory and that <TunnelName> is distinct for each certificate. The script outputs a certificate and key pair in <code>./ssl/clients/</code>.

=== Enabling Certificate based tunnels on server ===
To enable the use of certificates for tunnel authentication on a Bondix server, the configuration file /etc/bondixserver.json must be edited and the parameter <code>"rootCA":"client-root.crt"</code> needs to be added.
'''Example:'''

<code>{"target": "server", "action": "add-https","rootCA":"client-root.crt", "host": "0.0.0.0", "port": "443", "allowMonitor": true},</code>

=== Configuring the Client for Certificate Authentication ===
[[File:Client Certificate Config.png|thumb|Client Certificate Auth configuration]]
On the client side, select 'Certificate' as the 'Config Mode' and input the generated certificate/key pair. Additionally, configure the server's hostname or IP address. The tunnel will then appear on the server without requiring further setup.

= Additional Options =
== Setting Up Tunnel Limits ==
To manage the number of clients connected to the server when using certificate authentication, introduce a soft limit on the total active tunnels with the following configuration in <code>/etc/bondixserver.json</code>:

{"target": "tunnel", "action": "set-tunnel-limit", "maxTunnel": 100, "gracePeriod": 30},

* '''maxTunnel''' determines the maximum active tunnels. Exceeding this limit prompts tunnels to connect to an alternate server, configured either as a secondary server on the client or through a hostname with multiple IP records.
* '''gracePeriod''' is the duration in seconds allowing a previously rejected tunnel to reconnect without denial, ensuring connectivity even when resources on secondary servers are unavailable.

== Auto-Removing Stale Certificate Tunnels ==
To address fluctuation in tunnels utilizing certificate authentication, enable automatic tunnel removal with the following addition to /etc/bondixserver.json:

{"target": "tunnel", "action": "set-tunnel-autoremove", "enabled": true, "timeout": 600}

* '''timeout''' sets the lifespan of a certificate-based tunnel on the server in seconds, facilitating the management of active tunnels.

After making changes to <code>/etc/bondixserver.json</code> , the service must be restarted via <code>systemctl restart bondix</code>

Client Configuration

2026-06-11T11:41:26Z

Sylvia:

[[Category:General]]
= Commands =
A JSON command has the following structure:
<code>{"target": "<module>", "action": "<command>", [...additional values...]}</code>, where <module> specifies the configuration submodule and <command> specifies what should be done.

== Tunnel Commands ==
{| class="wikitable"
|-

|
=== create ===
Sets up basic tunnel configuration.
{| class="wikitable"
|+ Parameters
|-
| name || Tunnel Name. Required.
|-
| password || Password. Required.
|-
| server || Endpoint target IP. Optional.
|-
| interfaceName|| Desired name of the virtual tunnel network interface. Optional.
|-
| values || A JSON object containing configuration parameters for the tunnel.
|}
| style="width: 40%"|
<nowiki>{"target": "tunnel",
"action": "create",
"name": "MyTunnel",
"password: "1234",
"server": "10.0.0.1",
"interfaceName": "bndx0",
"values": {...}
}</nowiki>
|-

|
=== add-server ===
Adds a endpoint server. If multiple servers are added, the client will cycle through
them until a connection has been established successfully.
{| class="wikitable"
|+ Parameters
|-
| host|| IP or host of the destination server. Required.
|-
| port || Port of the destination server. Optional (Default: "443").
|}
||
<nowiki>{"target": "tunnel",
"action": "add-server",
"host": "10.0.0.1",
"port": "443"
}</nowiki>
|-

|
=== add-interface ===
Adds a single interface to the tunnel.
{| class="wikitable"
|+ Parameters
|-
| interface || Name of the linux network interface. Required.
|-
| name || Human-readable name for the interface. Optional.
|-
| preset || [[Client/Presets|Preset]] that should be applied to this interface. Optional.
|-
| values || Configuration values for this interface. See [[Tunnel Settings]]. Optional.
|}
||
<nowiki>{"target": "tunnel",
"action": "add-interface",
"interface": "wlan0",
"name": "WiFi",
"preset": "mobile",
"values": {"enabled": false}
}</nowiki>
|-

|
=== create-interfaces ===
Creates channels for the specified interfaces using [[Client/Presets|presets]].
{| class="wikitable"
|+ Parameters
|-
| interfaces|| a JSON object where each key is a network interface name, with the corresponding value being a [[Client/Presets|preset]] name. Required.
Instead of a preset name, an object with various interface settings can be specified, as specified in [[#update-interfaces]]
|}
||
<nowiki>{"target": "tunnel",
"action": "create-interfaces",
"interfaces": {
"wwan0": "mobile",
"eth1": "ethernet"
}
}</nowiki>
|-

|
=== delete ===
Resets the complete tunnel configuration, including interfaces.
||
<nowiki>{"target": "tunnel",
"action": "delete"
}</nowiki>
|-

|
=== enable-layer2 ===
Instructs the client to establish a layer 2 tunnel. Layer 2 must also be enabled on the server, otherwise the tunnel will fall back to layer3. Combining layer2 with BondingProxy is currently not supported.

When enabled, the client will create a tap interface and call bridgeutils (brctl) to automatically add this interface to the specified bridge.
{| class="wikitable"
|+ Parameters
|-
| bridge || The name of the network bridge that should be used. Required.
|-
| tapname || Name of the virtual tap interface. Optional, a dynamic name will be used when no name is supplied.
|}
||
<nowiki>{
"target": "tunnel",
"action": "enable-layer2",
"bridge": "br-lan",
"tapname": "bondixTap0"
}</nowiki>
|-

|
=== enable-proxy ===
Enables [[Bonding Proxy]].

{| class="wikitable"
|+ Parameters
|-
| host || Host where the bonding proxy server should listen on.
|-
| port || Port to be used with the bonding proxy server.
|-
| interface || Interface from which outgoing tcp connections should be proxied.
|}
||
<nowiki>{
"target": "tunnel",
"action": "enable-proxy",
"host": "0.0.0.0",
"port": "18080"
}</nowiki>
|-

|
=== disallow-swap ===
Explicitly tells the linux kernel to prevent memory swapping (mlockall).
||
<nowiki>{
"target": "tunnel",
"action": "disallow-swap"
}</nowiki>
|-

|
=== quicksetup ===
Sets up client using a base64 encoded JSON string containing connection info.

{| class="wikitable"
|+Parameters
|-
|data||base64 encoded JSON string with the following layout:
{"t": "TUNNELNAME", "p": "TUNNELPASSWORD", "s": "SERVER", "sp": "SERVERPORT", "bs": "BACKUPSERVER", "bp": "BACKUPSERVERPORT"}
"t", "p" and "s" are required, "sp", "bs" and "bp" are optional. If no server port is provided, port 443 will be used.

Creating a quickconnect code in Linux:
$ echo "{\"t\":\"TUNNELNAME\",\"p\":\"TUNNELPASSWORD\",\"s\":\"SERVER\"}"|base64
eyJ0IjoiVFVOTkVMTkFNRSIsInAiOiJUVU5ORUxQQVNTV09SRCIsInMiOiJTRVJWRVIifQo=
|}

||
<nowiki>{"target": "tunnel",
"action": "quicksetup",
"data": "..."
}
}</nowiki>
|-

|
=== set===
Sets tunnel properties. See [[Tunnel Settings]].
{| class="wikitable"
|+Parameters
|-
| values||JSON object with values to change. Required.
|}
||
<nowiki>{"target": "tunnel",
"action": "set",
"values": {"maxConcurrentChannel": 2}
}</nowiki>
|-

|
===set-meta===
Allows to add custom information that is shown on the server's tunnel status page. It has no further effect.
{| class="wikitable"
|+Parameters
|-
|data||Flat JSON object with custom info
|}
||
<nowiki>{
"target": "tunnel",
"action": "set-meta",
"data": {"location": "Test Lab", "customer": "Evil Corp"}
}</nowiki>
|-

|
===set-remote===
Sets tunnel properties on the remote end. See [[Tunnel Settings]].
{| class="wikitable"
|+Parameters
|-
|values||JSON object with values to change. Required.
|}
||
<nowiki>{"target": "tunnel",
"action": "set-remote",
"values": {"maxConcurrentChannel": 2}
}</nowiki>
|-

|
===set-interface===
Sets tunnel interface properties. See [[Tunnel Settings]].
{| class="wikitable"
|+Parameters
|-
|index|| Index of the channel. 0 for first created channel, 1 for second, etc..
|-
|values||JSON object with values to change.
|}
||
<nowiki>{"target": "tunnel",
"action": "set-interface",
"index": 0,
"values": {"enabled": false}
}</nowiki>
|-

|
===set-remote-interface===
Sets interface properties on the remote end. See [[Tunnel Settings]].
{| class="wikitable"
|+Parameters
|-
|index|| Index of the channel. 0 for first created channel, 1 for second, etc..
|-
|values ||JSON object with values to change.
|}
||
<nowiki>{"target": "tunnel",
"action": "set-remote-interface",
"index": 0,
"values": {"enabled": false}
}</nowiki>
|-

|
=== set-preset===
Applies a tunnel preset. See [[Client/Presets|Presets]] for more info.
{| class="wikitable"
|+Parameters
|-
|name|| Name of the tunnel preset. Required.
|}
||
<nowiki>{"target": "tunnel",
"action": "set-preset",
"preset": "Bonding"
}</nowiki>
|-

|
===set-ifname===
Renames the virtual network tunnel interface.
{| class="wikitable"
|+Parameters
|-
|name ||The name that the interface should be renamed to. Required.
|}
||
<nowiki>{"target": "tunnel",
"action": "set-ifname",
"name": "bondix0"
}
}</nowiki>
|-

|
===set-cert-check===
Enables or disables verification of the server's SSL certificate. ''TODO: Which root cert dir is used when no custom root certificate is provided?''
{| class="wikitable"
|+Parameters
|-
|enabled||Enables or disables SSL certificate verification. Required.
|}
||
<nowiki>{"target": "tunnel",
"action": "set-cert-check",
"enabled": true
}
}</nowiki>
|-

|
===set-root-ca===
Specifies a root certificate that can be used to verify the authenticity of the remote server. When used, SSL server verification will be automatically enabled.
{| class="wikitable"
|+ Parameters
|-
|file ||location of the public root certificate file. Required.
|}
||
<nowiki>{"target": "tunnel",
"action": "set-root-ca",
"file": "/etc/ssl/foobar.pub"
}
}</nowiki>
|-

|
===set-certificate ===
Loads a tunnel client certificate. See [[Certificates]] for further information.
{| class="wikitable"
|+Parameters
|-
|cert||location of the public certificate file. Required.
|-
|key||location of the private certificate key file. Required.
|}
||
<nowiki>{"target": "tunnel",
"action": "set-certificate",
"cert": "/etc/ssl/foobar.pem"
"key": "/etc/ssl/foobar.key"
}</nowiki>
|-

|
===embed-certs===
A helper functions to embed tunnel & root certificate inside the configuration instead of an external file. Performs the same actions as set-certificate and set-root-ca combined.
{| class="wikitable"
|+Parameters
|-
|cert ||The tunnel public certificate as string. Required.
|-
|key || The tunnel private certificate key as string. Required.
|-
|root||The public root certificate for server verification. Required.
|}
||
<nowiki>{"target": "tunnel",
"action": "embed-certs",
"cert": "...",
"key": "...",
"root": "..."
}</nowiki>
|-

|
===set-root-ca===
Specifies a root certificate that can be used to verify the authenticity of the remote server. When used, SSL server verification will be automatically enabled.
{| class="wikitable"
|+Parameters
|-
|file||location of the public root certificate file. Required.
|}
||
<nowiki>{"target": "tunnel",
"action": "set-root-ca",
"file": "/etc/ssl/foobar.pub"
}
}</nowiki>
|-

|
===update-interfaces===
Updates interface information. If a provided interface already exists, it will be updated accordingly. If a provided interface is new, it will be created. Interfaces that have been previously defined but are not provided here will be removed.
{| class="wikitable"
|+Parameters
|-
|interfaces||JSON Object with interfaces. Key specifies the linux WAN interface to be used (e.g. "eth1"), with its value being an object with the following properties.
|}
{| class="wikitable"
|+Object Parameters
|name
|string; Interface name that is shown in logs and in the endpoint webinterface.
|-
|preset
|string; Interface preset to be used (e.g. "mobileAggressive", "ethernet",...}
|-
|upstream
|object; {"min": 0, "max": 100}. "min" and "max" specfiy lower and upper bandwidth limits in MBit/sec for outgoing traffic (towards endpoint). A value of "0" means no limit. When a minimum value is specified, make sure that the value is below the maximum throughput of the interface to avoid congestion.
|-
|downstream
|object; {"min": 0, "max": 100}. "min" and "max" specfiy lower and upper bandwidth limits in MBit/sec for incoming traffic (from endpoint). A value of "0" means no limit. When a minimum value is specified, make sure that the value is below the maximum throughput of the interface to avoid congestion.
|-
| standby
|boolean; When enabled, the interface will go into standby if other sufficient interfaces are available, as specified by the "minimum connected channel" value configured. When in standby, Bondix will make no traffic through this interface until reactivated (e.g. due to a different interface going down). You can change the minimum number of connected channel by adding this command in bondixclient.json:
<nowiki>{"target": "tunnel", "action": "set", "values": { "minConnectedChannel": 2 }}</nowiki>
|-
|maxLatency
| number; overrides the maximum latency setting in milliseconds. Any packet exceeding this latency limit will be considered as lost, and the interface will not be used until latency is below the specified maximum. We do not encourage exposing this setting as it can have a negative impact on performance/throughput. (Default value is 1000 ms;
|-
| enabled
|boolean; If disabled, the interface will not be used, but still shown in the webinterface.
|}
Note: Updating the preset will override upstream, downstream, maxLatency & standby settings to default values.
||
{
"target": "tunnel",
"action": "update-interfaces",
"interfaces": {
"eth1": {
"name":"WAN1",
"preset": "mobileAggressive",
"upstream": {"min": 0, "max": 50},
"downstream": {"min": 0, "max": 100},
"standby": false,
"maxLatency": 1000,
"enabled": true
},
"eth2": {
"name":"WAN2",
"preset": "mobileAggressive",
"upstream": {"min": 0, "max": 50},
"downstream": {"min": 50, "max": 100}
}
}
|-

|
===update-packetSize===
Updates the maximum size that UDP packets may carry. Changing this value will cause a tunnel restart.
{| class="wikitable"
|+Parameters
|-
|value||Packet size value. Required. Valid range: 500 to 1400.
|}
||
<nowiki>{
"target": "tunnel",
"action": "update-packetSize",
"value": 1400
}</nowiki>
|-
|
===cloudlink===
Instructs the client to use Unwired® Cloudlink to retrieve its tunnel configuration. The client will use the provided API key and the mac address of the specified interface to authenticate itself.
A CA file must be provided in order to properly validate the SSL certificate of the CloudLink API endpoint.

''This command should not be used in combination with "create" to configure tunnel credentials or "add-server" to configure a target server.''
{| class="wikitable"
|+Parameters
|apiKey
|The CloudLink API key used for authentication. This key can be obtained by registering at https://admin.wifi.unwired.at
|-
|interface||The name of a linux interface whose mac address should be used for identification. Required.
|-
|caFile
|Location of a root certificate used for SSL validation of the CloudLink API endpoint.
|}
|
{
"target": "tunnel",
"action": "cloudlink",
"apiKey": "CLOUDLINK-API-KEY",
"interface": "eth0",
"caFile": "/etc/ssl/certs/ca-certificates.crt"
}
|}

==Interactive Commands==
Interactive commands can be used to interact with the tunnel and retrieve various information via the CLI socket.
''TODO: Add JSON responses''
{| class="wikitable" style="width: 100%"
|-

|
===get===
Returns all [[Tunnel Settings|tunnel settings]].
| style="width: 40%" |
<nowiki>{"target": "tunnel",
"action": "get"
}</nowiki>
|-

|
===get-interface===
Returns [[Tunnel Settings|settings]] for a specific interface.
{| class="wikitable"
|+Parameters
|-
|index||Index of the interface to fetch information from.
|}
||
<nowiki>{"target": "tunnel",
"action": "get-interface",
"index": 0
}</nowiki>
|-

|
===status===
Returns current tunnel information.
||
<nowiki>{"target": "tunnel",
"action": "status"
}</nowiki>
|-

|
===reset===
Performs a disconnect & reconnect.
||
<nowiki>{"target": "tunnel",
"action": "reset"
}</nowiki>
|}

==System Commands==
{| class="wikitable"
|-

|
===shutdown===
Shuts down the client and terminates.
| style="width: 40%" |
<nowiki>{
"target": "system",
"action": "shutdown"
}</nowiki>
|-

|
===set-log ===
Enables logging to file or changes output file.
{| class="wikitable"
|+Parameters
|-
|file||The filename that the log should be written to. Required.
|-
|fileMode||can be <code>append</code> or <code>overwrite</code>. Required.
|}
||
<nowiki>{
"target": "system",
"action": "set-log",
"file": "/var/log/saneclient.log",
"fileMode": "append"
}</nowiki>
|-

|
===set-script-path===
Changes the directory that points towards the client scripts. (/opt/bondix/client/scripts by default)
{| class="wikitable"
|+Parameters
|-
|path|| Path to the new bondix script directory.
|}
||
<nowiki>{
"target": "system",
"action": "set-script-path",
"path": "/etc/bondix/scripts"
}</nowiki>
|-

|
===set-webinterface===
Enables the integrated webserver & debug webinterface.
{| class="wikitable"
|+Parameters
|-
|host|| IP that the service should listen on. Required.
|-
|port||TCP Port that the service should listen on. Required.
|-
|allowConfig||En- or disables web configuration. Not required, enabled by default.
|-
|allowMonitor||En- or disables web monitor. Not required, enabled by default.
|-
|configApiKey||The password required to access the realtime monitor monitor.
|-
|webroot||Web root directory. Points to the "www" subdirectory in installation directory. Not required, changing not advised.
|}
||
<nowiki>{
"target": "system",
"action": "set-webinterface",
"host": "0.0.0.0",
"port": "80",
"allowConfig": false,
"allowMonitor": true,
"configApiKey": "123456",
"webroot": "/tmp/"
}</nowiki>
|}

Client/RUTX12

2026-06-11T11:41:07Z

Sylvia:

[[Category:General]]
The Teltonika RUTX12 is an OpenWRT based router with two 4G modems.
= Installation =
See [[Client/OpenWRT]]

= Tips & Tricks =
== Enable "Force Link" for 4G modems ==
This seems to be required, as the secondary modem seems to not connect under certain circumstances, wehn the first modem is active. "Force Link" ensures that both modems get always connected

== Switch Configuration for extra WAN ==
* Go to Network > VLAN > Port Based
* Choose the LAN port you want to turn into a WAN port. Set the port to "off" in VLAN 1
* Add a VLAN, set your desired port to "Untagged", while leaving everything else at "off"
* Go to Network > Interfaces
* create a new interface (e.g. "wan2"). Protocol "dhcp", physical interface "eth0.x" (x being a number, e.g. 2), firewall zone "wan"
* edit SANE configuration file, add interface using "eth0.x"

Client

2026-06-11T11:40:50Z

Sylvia:

[[Category:General]]
The Bondix SANE client is the software that you install on your router, which establishes a connection to the [[Server|server]] using multiple WAN links. The software itself is a linux userspace program, but installation packages for different routers are available, that take care of most of the configuration.

This page covers the barebone linux application. Please check out the [[Teltonika]] page for installation & usage on these routers.

==Configuration==
Configuration is done using [https://www.json.org/ JSON] commands. These can either be sent via a raw TCP socket (localhost:5113), or written to a configuration file (in a json-array) that is parsed on start-up.

By default, SANE checks for the existence of a configuration file in its installation directory (e.g. <code>/opt/bondix/client/bondixclient.json</code>) and at <code>/etc/bondixclient.json</code>. If you want SANE to load a configuration from a different location, you can specify it using a command line parameter.

===Quick Start===
This example provides the minimal necessities to get a tunnel up and running:
<nowiki>[
{"action": "create", "target": "tunnel", "name": "TUNNELNAME", "password": "TUNNELPASSWORD"},
{"action": "add-server", "target": "tunnel", "host": "ENDPOINTSERVER", "port": "443"},
{"action": "create-interfaces", "target": "tunnel", "interfaces": {
"eth1": "mobileAggressive",
"wwan0": "mobileAggressive",
"wwan1": "mobileAggressive"
}},
{"target": "tunnel", "action": "set-preset", "preset": "bonding"}
]
</nowiki>

===Configuration Commands===
For a complete reference list of available commands, see [[Client Configuration]].

===Tunnel Configuration===
Tunnels and channels have many configurable values, that are managed using [[Presets]].

=Running=
The software can be run in the shell using <code>/opt/bondix/client/saneclient</code>, where it will run in the foreground. However, it is recommended to start the service automatically on startup, which can be different depending on the platform.

===Parameters===
{| class="wikitable"
|-
|<code>--daemon</code>||Runs the software as a daemon.
|-
|<code>--nopid</code>|| Does not attempt to create a pid-file at <code>/var/run/saneclient.pid</code>
|-
|<code>--listflags</code>||Lists available feature flags
|-
|<code>--flags <FLAG1> <FLAG2>... </code>||Enables the specified flag(s). Multiple flags are separated using space.
|-
|<code></path/to/filename.json></code>||JSON configuration file that should be used
|}

===Feature Flags===
Feature flags are switches that enable certain features that are otherwise unavailable. These features are usually experimental and should be used with caution.
{| class="wikitable"
|-
|useBlake||Switches from SHA256 to the "blake" hashing algorithm.
|-
|useBlake3||Switches to the "blake3" hashing algorithm.
|-
|disableHash||Disables hashing completely
|-
|useMMSG||uses useMMSG linux socket API to send & receive multiple UDP packets at once.
|-
|channelRoutes||Makes the client create specific routes for each channel. Experimental, do not use.
|-
|bondingProxy||<s>Enables the TCP [[Bonding Proxy]]</s>. Now always enabled
|}

==bndutil==
bndutil is a command line utility that allows to query and modify SANE during runtime. It uses the configuration TCP socket
<nowiki>root@Teltonika-RUTX12:/opt/bondix/client# ./bndutil
Usage:
bndutil [--json] <command>
--json switch to JSON output

Available commands:
* bndutil status
* bndutil get
* bndutil set <propertyName1> <propertyValue1> [propertyName2] [propertyValue2] ...
* bndutil get-interface <index>
* bndutil set-interface <index> <propertyName1> <propertyValue1> [propertyName2] [propertyValue2] ...
* bndutil shutdown
* bndutil restart
(tunnel reset & reconnect)
</nowiki>

==speedtest==
Speedtest is a small utility that downloads (and discards) data via HTTP(s) using one or more WAN interfaces. It is useful to compare performance of each individual interface and the combined bandwidth over SANE's virtual tunnel interface.
<nowiki>root@Teltonika-RUTX12:/opt/bondix/client# ./speedtest
Usage: speedtest [--json] <download-url> <intf1> [intf2] ...</nowiki>

E.g., to test performance of each WAN interface directly:
<nowiki>./speedtest http://speed.hetzner.de/100MB.bin wwan0 wwan1 wwan2</nowiki>

Testing performance of the tunnel:
<nowiki>./speedtest http://speed.hetzner.de/100MB.bin tun0</nowiki>

Starlink

2026-06-11T11:40:38Z

Sylvia:

[[Category:General]]
[https://www.starlink.com/ Starlink] can easily be integrated into Bondix, which many of our our customers already do. However, it always needs to be combined with mobile communications because of the following downsides:

* High energy consumption
: The antenna draws an average of 130 to 150 Watts which makes mobile operation based on battery difficult. For comparison: A Teltonika router draws around 15 to 20 Watts with 2 active modems.
* Line of sight required
: As is usual with SAT systems, a clear view of the sky must be guaranteed at the antenna location. This can be problematic in industrial plants with many nooks and crannies, especially in your tank farms. If may be necessary that the antenna must be placed far away from your RDU for which very long network cables may have to be installed. This, in turn, can result in lower throughput.
* Monthly fixed costs
: The monthly fixed costs for such a system ([https://www.starlink.com/business Starlink Business]) are around € 214,00 per month for 1 TB, plus a one-off cost for the hardware of around € 600,00 per set.

Client/StaticRoutes

2026-06-11T11:40:23Z

Sylvia:

[[Category:General]]
== How to create static routes in the web interface ==

"Interface" must be set towards the interface that should be used as a first hop, where the device providing VPN is. This depends on your network/VPN setup.

"Target" and "IPv4 Netmask" should be set according to the IP subnet used in your VPN (100.64.8.0 255.255.255.0 ?)

Metric, MTU and Route Type can be left as is. To save, make sure to press "Save & Apply" at the bottom of the page instead of the "Add" button seen in the screenshot.

Again, the reason why this happens is likely that you are accessing the router with a source IP address that is within the LAN IP subnet. With Bondix disabled, the router will use its regular default route, which happens to route the responses to your device accordingly. However, when Bondix is enabled, the default route changes to go through the tunnel, bypassing your regular VPN routing setup.

If you are still unsure, log into the router via SSH through your VPN setup when the bondix tunnel is disabled. To find out which IP the router sees, you can do a

<nowiki>logread | grep dropbear</nowiki>

The last line should be something along "Password auth succeeded for 'root' from 10.24.0.2:57401".
(But of course with your IP instead.)

Now, do a traceroute for that IP on the device:

The first hop reveals which gateway IP to put in the static route, based on this you can also determine which interface must be configured. If you are unsure about the netmask, you can use 255.255.255.255 to only route your IP.

DMZ and 1:1 NAT configuration

2026-06-11T11:40:14Z

Sylvia:

[[Category:General]]
= DMZ and 1:1 NAT configuration with additional static, public IPv4 addresses on the Bondix server =

This page describes how to forward traffic from a public IP on the Bondix server to a LAN host behind an Bondix client router using iptables and port forwarding.

== Assumptions ==

* You are operating your own Bondix server with the option to get additional public IPv4 addresses.
* You have an additional IP address on the Bondix server (example: '''''14.15.16.1''''').
* The LAN client behind the OpenWRT router has a private IP address like '''''192.168.5.213'''''.

== Step 1: Configure additional IP address on the server ==

Configure the additional IP address (e.g. '''''14.15.16.1''''') on the Bondix server based on the instructions of your server provider.

== Step 2: Create a new environment in the Bondix Server GUI ==

1. Log in to the Bondix server GUI.

2. Create a **new environment**.

[[File:Addenv1.png|none|825x825px]]

3. In this environment, set:

*'''Outgoing NAT IP''' = ''14.15.16.1''
[[File:Add_nat_ip.png|none|460x460px]]

== Step 3: Add iptables rules on the Bondix server ==

Determine the Bondix client interface IP in the tunnel (e.g. from the tunnel status page when the client is connected).
It will look like: ''169.254.xxx.xxx'' (example here: ''169.254.20.4'').

[[File:Stats.png|frameless|484x484px]]

Then add the following iptables rules on the Bondix server shell:

'''''iptables -A PREROUTING -t nat -d 14.15.16.1 -j DNAT --to 169.254.xxx.xxx'''''

'''''iptables -A FORWARD -d 169.254.xxx.xxx -j ACCEPT'''''

Replace:

* ''14.15.16.1'' with your actual additional IP on the server (if different).
* ''169.254.xxx.xxx'' with the actual tunnel client IP of the Bondix client.

== Step 4: Configure port forwarding on the OpenWRT router ==

In the firewall of the Bondix client router:

1. Open the **Port Forwarding / Firewall** configuration.
2. Create a rule forwarding **all traffic from the Bondix zone** to the LAN client IP address:

* From zone: **Bondix**
* To IP: **192.168.5.213** (LAN host)

Set protocol to all as needed for your use case.

Example screenshot from Teltonika:

[[File:Dmz teltonika.png|frameless|791x791px]]

== Step 5: Make iptables rules persistent ==

By default, iptables rules are **not persistent** and will be lost after a reboot.

To ensure the rules are always applied:

* Use a tool like '''iptables-persistent''', **or**
* Create a Linux service / script that runs these iptables commands on boot.

== Step 6: Reserve a fixed tunnel client IP (optional but recommended) ==

Once everything works, it is recommended to reserve the tunnel client IP for this specific Bondix tunnel client.

On the Bondix server:

1. Open the tunnel configuration for this client.
2. Set the desired fixed tunnel IP in the **Tunnel Client IP mask**, e.g.:

* '''Tunnel Client IP mask''' = ''169.254.19.4''

[[File:Fixedip.png|frameless|732x732px]]

This ensures the tunnel client always receives the IP address ''169.254.19.4''.

== Step 7: Final iptables rules with fixed tunnel IP ==

If you reserve the tunnel client IP (e.g. ''169.254.19.4''), update your iptables rules accordingly:

'''iptables -A PREROUTING -t nat -d 14.15.16.1 -j DNAT --to 169.254.19.4'''

'''iptables -A FORWARD -d 169.254.19.4 -j ACCEPT'''

With these settings:

* Traffic to ''14.15.16.1'' on the Bondix server is DNATed to '''''169.254.19.4''''' (tunnel client).
* The OpenWRT client forwards this traffic from the Bondix zone to the LAN client '''''192.168.5.213'''''.

If you have further questions or special requirements, please contact support.

QuickConnect

2026-06-11T11:40:03Z

Sylvia:

[[Category:General]]

== Quick Connect Format ==
A quick connect code is BASE64 encoded JSON. It can either contain tunnel credentials to a server, or point to a 3rd party orchestration server, to which the client connects and receives its connection details.

==== With embedded credentials: ====
{"t":"<Tunnel>", "p":"<Password>", "s": "<Server>", "p": "<Server-Port>", "b": "<Backup-Server>", "bp": "<Backup-Server-Port>"}
Server port & backup server (+ port) are optional. If no port is provided, port "443" is assumed.

Tunnel Name, password & server are required.

==== With Orchestration server URL: ====
<nowiki>{"u": "Orchestration Server URL", "m": {"meta": "data"}}}</nowiki>

== Orchestration Server Protocol ==
When the client is started with a quick connect code that points to an orchestration server, it sends a HTTP POST request to the provided URL.

==== Client Request ====
<nowiki>{"action":"request", "version":"1", "info": {"architecture": "X86_64/Common KVM processor", "build":"20221130-0939-8e0de0d"}, "meta": {"meta": "data"}}</nowiki>
{| class="wikitable"
|+
!Property
!Description
|-
|action
|The type of request. The following values are valid:

* request - initial request when the device is asking for credentials
* ping - ping request when the device is connected
* ping-down - ping request when the device has received credentials, but the tunnel is not connected
|-
|version
|Protocol version. For now, this field is "1".
|-
|info
|Various information gathered from the client device, such as architecture and build version. Available information might vary depending on platform and build.
todo add fingerprint info
|-
|meta
|Optional custom meta-data that is encoded in the connection string ("m").
|}

==== Server Response ====
{"result": "ok", "version": 1, "tunnel":"test1", "password":"test", "server":"10.42.0.11", "keepAlive":360, "keepAliveDown":1}
{| class="wikitable"
|+
!Property
!Description
|-
|result
|Should contain "ok". Any other value will cause the client to disable the tunnel.
|-
|server
|Target server. Should be an IP address
|-
|tunnel
|Tunnel name
|-
|password
|Tunnel password
|-
|keepAlive
|Interval in minutes in which a keep alive request should be sent when the tunnel is connected. If the value is omitted or -1, no keep alive intervals will be sent while the tunnel is connected.
|-
|keepAliveDown
|Interval in minutes in which a keep-alive request should be sent when the tunnel is not connected. If no value is supplied, 1 minute is assumed.
|}
If the server is not reachable, responds with a non 200 HTTP return code, or if the response contains invalid JSON, the request is considered failed. In this case, the next request will be done either 5 seconds later, or after the time specified in keepAlive/keepAliveDown.

=== Ping Requests ===
The client can send periodical pings to an orchestration server, which can be used to update credentials or track activity.

When the client tunnel is connected, the interval provided by the "keepAlive" property is used - if the value is -1, no requests are sent as long as the tunnel is connected.

If the client is not able to connect the tunnel, the interval provided by the "keepAliveDown" property is used instead. Unlike regular ping, this type of request cannot be disabled.

Presets

2026-06-11T11:39:51Z

Sylvia:

[[Category:General]]
Presets provide different configuration options for a tunnel and its used interfaces.

Presets are stored in "presets.json" on both client and server installations. Some presets are not directly accessible in router packages, as some of them are redundant and only kept for compatibility.

== Tunnel Presets ==
{| class="wikitable"
|+
!Preset Name
!Friendly Name
!Description
|-
|bonding
|(Default) Bonding
|The default bonding strategy. Uses least amount of interfaces if possible, ranging from best to worst.
|-
|bondingDistribute
|Bonding with enforced distribution
|Bonding with enforced distribution. This mode can increase latency jitter and degrade performance in situations where an excellent line (e.g., fiber) is mixed with a mediocre to bad line (e.g., bad 4G).
|-
|duplication
|Packet Duplication
|Attempts to send each data fragment twice using different interfaces. Packet duplication is not guaranteed (e.g. if only one WAN interface is available)
|-
|duplication2
|Packet Duplication 2X
|Like packet duplication, but each data fragment is used over up to three interfaces.
|-
|failover
|Seamless failover
|Seamless or smart failover only uses one interface at a time. If the primary interface goes down, a secondary interface will be used without interrupting any connections.
|-
|loadbalancer
|Load Balancing Mode
|Experimental Load Balancing mode. Not recommended.
|}

== Channel Presets ==
{| class="wikitable"
|+
!Preset Name
!Friendly Name
!Description
|-
|mobileAggressive
|Optimize for Speed
|This default preset is a general-purpose configuration suitable for most lines (4G, DSL, etc), with a fair tolerance for packet loss and latency.
|-
|ethernet
|Default Ethernet
|A preset for direct ethernet connections, very sensitive to latency and packet loss.
|-
|genericTCP
|TCP Mode
|Utilizes TCP instead of UDP. Higher throughput rate at the cost of latency. Useful in scenarios where UDP is throttled or blocked.
|-
|lowLatency
|Low Latency
|Similar to ethernet preset, but with higher tolerance for packet loss
|-
|mobile
|Mobile
|A general purpose preset for mobile connections favouring latency
|-
|mobileLowLatency
|Optimize for Latency
|Another preset for mobile connections with an even higher focus on latency
|}

Layer2

2026-06-11T11:39:40Z

Sylvia:

[[Category:General]]

== Client Setup ==

* Create separate VLAN interface (Protocol: None, no firewall zone, '''bridge Interfaces''')
** Step 1: create port based VLAN (Network > VLAN > Port Based). Here we use LAN4 to create a new VLAN with ID 4. [[File:Image.png]]
** Step 2: Create Interface (Network > Interfaces > Create New Interface) with the following properties:
*** (General Settings) Protocol: '''none'''
*** (Physical Settings) Bridge Interfaces: '''yes'''
*** (Physical Settings) Interface: '''eth0.3''' (your newly created interface)
*** (Firewall Settings) Firewall zone: '''unassigned'''
** Step 3: Enable Layer2 Bonding in Bondix Settings (Network > Interfaces > Bondix Bonding). Select your newly created interface as bridge interface.

== Server Setup ==

*Create network bridge on Linux server
*Make sure that bridge-utils is installed
* Static IP Address
** via netplan: /etc/netplan/50-cloud-init.yaml, e.g.:
network:
version: 2
ethernets:
eth0:
<KEEP AS IS>
bridges:
sabr0:
addresses: [ 10.133.7.1/24 ]

* Configure DHCP server
** in /etc/dhcp/dhcpd.conf add:

subnet 10.133.7.0 netmask 255.255.255.0 {
range 10.133.7.26 10.133.7.250;
option domain-name-servers 8.8.8.8, 8.8.4.4;
option subnet-mask 255.255.255.0;
option routers 10.133.7.1;
option broadcast-address 10.133.7.255;
default-lease-time 600;
max-lease-time 7200;
}

* In Bondix Server, enable Layer 2 Bonding for the target tunnel(s). L2 Interface name can be left empty, L2 Interface bridge mut be set to configured bridge (e.g. sabr0)

Quality of Service

2026-06-11T11:39:24Z

Sylvia:

[[Category:General]]

==Basics==
[[File:QoS Editor.png|thumb|right|The QoS editor with a default rule.]]With Bondix Quality of Service settings, you can apply different bonding rules for different types of traffic. Traffic can be differentiated via packet type, source, and/or destination IP. Bonding rules allow for setting priority or duplication to limiting bandwidth or optimizing for latency.

===Server: QoS Presets===
On the server side, Bondix comes with a selection of QoS presets which can be used for quick configuration. In effect, Bondix QoS replaces Bondix Tunnel Presets. However, if QoS is to be initiated from the Client, make sure to choose "Custom QoS" in the Tunnel Presets of the General Settings.

Here are the Server's QoS presets at a glance:
{| class="wikitable"
|+
! Preset
!Description
|-
| style="width: 150px" |Bonding
|This is the default preset - bonding over any interface with BondingProxy enabled.
|-
|Bonding (No Proxy)
|Bonding with BondingProxy disabled.
|-
|Packet Duplication
|Default Bonding with packet duplication (1x) enabled.
|-
|Seamless failover
|Only use one interface as indicated by channel priority or latency.
|-
| Satellite
|A preset for satellite scenarios. Satellite is only used for HTTP(S) traffic, except when no other interfaces are available.
|-
|Default QoS
|A more sophisticated preset including a priority rule for DNS traffic, VoIP and online meetings.
|}
A QoS preset consists of one or more traffic groups (QoS group). When a client connects to a server, it sends along its desired QoS configuration which the server can either use or replace with a different configuration. The server also comes with a QoS preset editor which allows you to create custom presets that can be applied on multiple tunnels.
<gallery widths=400px heights=260px>
File:Bondix-123101-qos.png|thumb|QoS settings on Bondix Server
File:Bondix-123101-tunnel-qos.png|thumb|QoS presets for Tunnels on Bondix Server
File:Bondix-123101-qos-presets.png|thumb|QoS presets for Tunnels on Bondix Server, list
</gallery>

===Client & Server: Traffic Group===
A traffic group (QoS group) consists of a ruleset of how traffic should be handled, and a list of matching traffic types to which these rules shoule be applied to.

====Group Settings====
{| class="wikitable"
|+
!Property
!Description
|-
| style="width: 150px" |Name
|This is where you give your traffic group a short descriptive name that ideally describes the type of traffic you want to assign to it.
|-
|Score
| The group's score determines how often it gets the chance to send out data. The minimum value is 1, each additional score point gives the group a bigger slice of available data. Groups with higher score also get to write their data first. View this as a type of priority setting.
|-
|Packet Copies
|This value defines how many copies of each packet should be made. A value of 0 means no duplication, a value of 1 means single duplication, and so on. Packet Copies are opportunistic: If not enough interfaces are available to send the amount of configured copies, less copies will be made.
|-
|Latency Offset
|This setting describes the maximum difference that is allowed between the interface with the lowest and the one with the highest latency. With this setting, you can exclude slow or unreliable lines should their latency become too high. A value of 0 means no limitation.
|-
|Max Down (MBit)
|This value defines the maximum bandwidth allowed downstream in MBit. Downstream always refers to traffic sent from the server to the client. A value of 0 means no limitation.
|-
|Max Up (MBit)
|This value defines the maximum bandwidth allowed upstream in MBit. Upstream always refers to traffic sent from the client to the server. A value of 0 means no limitation.
|-
|Max Channel
|This value sets the maximum number of channels that should be used at once for this group. A value of 0 means no limit.
|-
| Channel Selection
|Here, you can define how channels are selected. These are the possible options:

* Default: This is the default method which considers configured priority, latency and reliability.
* Latency: This option only considers latency (lowest first).
* Bandwidth: This option only considers available bandwidth (highest first).
* Priority: This option only considers priority.
|-
|Bonding Proxy
|If enabled, matching TCP traffic will be bonded using BondingProxy which optimizes bonding throughput and efficiency.
|-
|Always Distribute
|If enabled, traffic is always spread through all interfaces. This is disabled by default as it usually introduces unnecessary jitter but may be beneficial if you're looking to spread traffic evenly across multiple interfaces.
|}

==== Matching Rules ====
Matching rules describe the type of traffic you want to assign to a group.
{| class="wikitable"
|+
!Property
!Description
|-
| style="width: 150px" |Traffic Type
|Possible options:

* Any - ignore traffic type
* TCP
* UDP
* TCP & UDP
* ICMP
* Other - everything else that is not on this list
|-
|Source
|Here, you define the source IP network in CIDR notation. In order to match properly, make sure to disable masquerading on the client. A value of "0.0.0.0/0" means traffic from any source.
|-
|Source Port
|Here, you define the source port. This can either be a single value (e.g. "80") or a range (e.g. "22-23"). A value of 0 means any port.
|-
|Destination
|Here, you give the destination IP network in CIDR notation. For individual IPs, make sure to include the network prefix /32. A value of "0.0.0.0/0" means traffic to any destination.
|-
|Destination Port
|Here, you give the destination port. This can either be a single value (e.g. "80") or a range (e.g. "22-23"). A value of 0 means any port.
|-
|DSCP
|Here, you specify the DSCP [[wikipedia:Differentiated_services|Differentiated Services Code Point]] value. A value of -1 means that packets with any DSCP value will match. This value is ignored in combination with Bonding Proxy.
|}
Traffic matching rules are sorted by specificity. That means that the most specific rules are checked on first, the broadest rule is checked last.

<gallery widths=400px heights=260px>
File:Bondix-123101-qos.png|thumb|left|QoS settings on Bondix Server
File:Tel-07045-network-bondixsane-qos.png|thumb|left|QoS settings on Bondix Client for Teltonika 07.04.5
File:Tel-07045-network-bondixsane-qos-detail.png|thumb|left|QoS settings on Bondix Client for Teltonika 07.04.5, Traffic Group detail
</gallery>

===Client: Teltonika===
[[File:Teltonika Preset Selection.png|right]]
If you want to use custom QoS settings on Teltonika routers, make sure that the preset is set to "Custom QoS" and that the assigned server allows Client QoS settings - otherwise the server will override any Client QoS settings. You can verify this via the Status page.

We recommend pushing QoS presets via the Bondix Server because then they're created and managed in a single place and don't have to manage the QoS settings on all routers individually.

==Compatibility==
Client and server are generally backwards compatible. When a legacy client connects to a QoS-enabled endpoint, the client can still apply its original tunnel preset (which is what QoS replaces). When a QoS-enabled client connects to a legacy server, it will always use the default "Bonding" tunnel preset, or the preset propagated by the legacy server.

== Best Practices ==

* Always create a default rule that matches to any traffic. Traffic without an appropriate matching rule will still be transmitted but performance results may vary.
* BondingProxy uses ''iptables'' rules to redirect matching TCP traffic. To exclude certain traffic from BondingProxy, create a new group with matching rules and the proxy disabled. This will create appropiate exclusion rules for ''iptables''.

Teltonika Portforwarding

2026-06-11T11:39:13Z

Sylvia:

[[Category:General]]

== General port forwarding settings ==
For TCP port forwarding a separate configuration of a forwarding on the router with the Bondix client is not necessary if:

* the port forwarding is configured via the web interface
* only TCP ports are forwarded
* the Bonding proxy is in use
* port forwarding is enabled in the Bondix client advanced settings.

For any kind of port forwarding which includes UDP ports, iptables (or equal) rules will be needed on the server side.

In this case, there is also a need to configure a port forwarding on the Bondix client router. For Teltonika see below.

== UDP Port Forward from a Teltonika router to the server ==
In this example, we are going to create two port forwardings to make a UDP port behind a Teltonika Router accessible via the endpoint's public IP. The first port forwarding will be created on the router, forwarding traffic from the Bondix tunnel towards the device in LAN. The second port forwarding will be created on the endpoint server, forwarding requests from it's public IP to towards the appropiate tunnel.

But first, lets make sure on the server that the tunnel in question is configured with a fixed IP, as it will make things much easier:

[[File:Fixed IP for tunnel.png]]

The IP must be part of the environment's virtual network which the tunnel used (169.254.xx.0/24 by default). In this example, we are using ''169.254.20.2.''

Next, go to the router's webinterface and navigate to Network > Firewall > Port Forwardings. In this example, we are going to create a port forwarding from a device in LAN towards the Bondix tunnel:

[[File:Teltonika Port Forward Settings.png]]

* Protocol: as required by your needs. Defaults to TCP+UDP, change to UDP.
* Source zone: "bondix" (where the request is coming from)
* External port: The port used for the forwarding. This port used here is just intermediate and can be used freely, although it is advised to use a port number higher than 1024.
* Internal zone: "lan" (where the request should be forwarded to)
* Internal IP address: the target device
* Internal port: the target port

In the firewall general settings, make sure that Masquerading for LAN => Bondix is enabled.

Finally, the second port forwarding must be set up on the server:
iptables -A PREROUTING -t nat -i eth0 -p udp --dport 20022 -j DNAT --to 169.254.20.2:12345
iptables -A FORWARD -p udp -d 169.254.20.2 --dport 20022 -j ACCEPT
Make sure that the following argument is correct:

* eth0 - the interface name used on your server might differ
* 20022 - this is the port that the will be used for forwarding, and will be publicly accessible.
* 169.254.20.2:12345 - the tunnel ip + intermediate port used.

FAQs

2026-06-11T11:38:56Z

Sylvia:

[[Category:General]]

''[[Main_Page|Start]] > [[Main_Page#Basics|Basics]] > [[FAQs]]''

Here, you'll find a list of frequently asked questions and their answers. This list will be continually updated.

== "Advanced Settings" tab missing on Teltonika router ==

Problem: There is no Advanced Settings tab after installing Bondix on a Teltonika router.

Solution: Switch your router into Advanced mode up top.
[[File:Networking rutx manual webui basic advanced mode.gif|frame|center]]
[[File:Wiki-faq-basic-adv.jpg|frame|center]]

== Stalling Bondix modems ==

Problem: Bondix modems lose their connections after 5 to 60 seconds during (high-volume) up- or downloads.

Solution: Check the power supply used to provide at least as much voltage and current as the router's original native power supply. Lower power supply can result in Bondix modems stalling after load is put on them.

Manuals/Webshop

2026-06-11T11:38:24Z

Sylvia:

[[Category:General]]

= How to order Bondix in our Webshop =

== Overview ==
This guide explains how you can order Bondix Licenses and Bondix Hosted Services via the webshop and manage access efficiently.

== Why use the Webshop? ==
The Bondix webshop is the fastest and most reliable way to order:

* Instant payment and delivery
* License codes available immediately
* Full visibility and management in your account
* Required for all subscription purchases

=== Key Benefits ===
* '''Zero waiting''' – licenses issued within seconds after payment
* '''Instant manageability''' – activate and assign immediately
* '''Operational clarity''' – everything centralized in one account
* '''Lower admin overhead''' – no manual processing required
* '''Future-proof''' – subscriptions only available via webshop

== Step-by-step: Ordering in the Webshop ==

=== 1. Log in ===
Go to:
* [https://shop.bondix.de shop.bondix.de]

Use your shared company email (recommended).

=== 2. Select products ===
Choose the required:
* Bondix Licenses
* Bondix Hosted Services
* Bondix License Subscription (coming soon!)

Find more information on our products here: [[product catalogue|Bondix Product Catalogue]]

=== 3. Complete payment ===
Supported payment methods:

* Credit Card
* PayPal
* Klarna (EU)
* Localized payment methods depending on region

=== 4. Receive licenses instantly ===
After successful payment:

* License codes are issued immediately
* Codes are visible in your webshop account
* Ready for immediate use or customer hand-off

=== 5. Manage licenses ===
In your webshop account you can:

* View all licenses and subscriptions
* Prepare customer hand-off
* Maintain full overview of purchases

== Account Setup (Recommended) ==

=== Use a shared company email ===
Example:
* bondix@yourcompany.com

Benefits:
* Central ownership of licenses
* Access for multiple team members
* Automatic application of partner discounts
* Same login works for:
** [https://shop.bondix.com/collections/all Bondix Webshop]
** [https://my.bondix.cloud my.bondix.cloud]

=== Optional: Register as Bondix Verified Customer ===
Open the [https://shop.bondix.de/pages/register Bondix Verified Customer Registration form].

Provide:
* Company details
* VAT ID (if applicable) or tax number

We'll review your application and get back to you as soon as possible.

== Bondix Hosted Services ==
* Must always be purchased via the webshop
* Cannot be ordered via invoice/email
* Managed directly in your webshop account

== Alternative: Purchase on Account (When to use) ==

Use only if:
* You order '''≥25 licenses''' AND
* You require invoice-based purchasing

=== How it works ===
Send order to:
* orders@sima.gmbh

Include:
* Company details
* Billing information
* Product and quantity
* Project/customer reference

=== Limitations ===
* Delivery: up to 5 working days
* No instant license visibility in webshop
* No subscriptions available
* Not suitable for urgent orders

== For Bondix Resellers and Bondix Partners Only: Best Practice - Customer Hand-off ==
For clean customer ownership:

# Create a dedicated customer email (e.g. customer@partner.com)
# Use this email for ordering in the webshop
# Log into my.bondix.cloud with this email
# Set password and hand over credentials to the customer

Benefits:
* Customer owns licenses and subscriptions
* Clean separation from partner accounts
* Enables customer self-service

== FAQ ==

; How fast is delivery?
Within seconds after successful payment.

; Can I mix webshop and invoice orders?
No. Use separate orders.

; Why are invoice-based licenses not visible in the webshop?
They are not automatically synchronized.

; Can subscriptions be invoiced?
No. Webshop only.

== Quick Decision Guide ==
* Need licenses immediately → '''Use webshop'''
* Ordering ≥25 licenses with invoice → '''Email order'''
* Buying subscriptions → '''Webshop only'''

== Links & Contacts ==
* Webshop: [https://shop.bondix.de shop.bondix.de]
* Orders (invoice): [mailto:orders@sima.gmbh orders@sima.gmbh]
* Partner support: [mailto:sales@sima.gmbh sales@sima.gmbh]

My.bondix.cloud

2026-06-11T11:38:11Z

Sylvia:

[[Category:General]]

This is your manual for [https://my.bondix.cloud my.bondix.cloud], your Bondix management portal: Monitor connections, subscriptions, and licenses tied to your email address—all in one secure and technical dashboard. This manual will show you how to login and what information each section gives you.

* Version: 1.0
* Last Updated: Nov 18, 2025

= Login =
<gallery widths=500 heights=300 mode="nolines">
File:1-login.jpg
File:1a-login-link.jpg
</gallery>
Navigate to [https://my.bondix.cloud my.bondix.cloud].

Enter your email address and click “Continue”.

Please make sure it is the same email address you used in our webshop ([https://shop.bondix.de shop.bondix.de]) to buy licenses and subscriptions.

[[File:1b-login-email.jpg|none|500px]]
Check your emails. Make sure to also check your spam folder.

You should receive an email from noreply@bondix.dev within 5 minutes with your login link.

= Home =
[[File:2-home.jpg|none|500px]]
This is your my.bondix.cloud Welcome Dashboard.
It shows you:
*Cloud: How many Essential Cloud services or subscriptions and their tunnels you’re currently running. Click the tab “Essential Cloud” to get more details.
* Licenses: How many Bondix Licenses you have active and in total. Click the tab “Licenses” to get more details.
* Servers: How many Bondix servers you’re currently running with how many active channels. Click the tab “Usage” to get more details.
* Next Expiry: Which of your Essential Cloud services or subscriptions will expire/renew next.

== Setting a new password ==
[[File:2a-profile.jpg|none|500px]]
Click the profile icon in the upper right corner.

The profile gives you three options:
* Change Password: Set a new password if you need to separate access to your my.bondix.cloud account from your email address.
* Toggle Theme: Switch between a dark and a light theme depending on your preferences.
* Sign out: Log out of your account.

[[File:2b-change-password.jpg|none|500px]]
Enter a new password in “New Password”, enter the same password again under “Confirm New Password”, and click “Change Password”.

Once you’ve logged out, logging in again will require your email address as user name and your newly set password.

= Essential Cloud =
== Status ==
[[File:3-essential-cloud.jpg|none|500px]]
For each of your Bondix Essential Cloud products, you’ll find a set of corresponding Tunnel Details and Channel Status. To know which one to look at, look up the IP address under “Server Instance”. On the right, you’ll see when it expires (or renews if it’s a subscription you haven’t cancelled yet). Just below, you’ll see whether it’s a “fixed expiry product” which means that after it expires, the connection code or tunnel credentials can no longer be used, or a subscription which means it renews automatically unless cancelled in time.

'''Tunnel Details''' gives you an overview over your tunnel’s statistics and tells you whether it’s connected, how many WAN links (“Connected Channels”) you’re actively using, which QoS rule applies, how long your tunnel has been running uninterruptedly and how much data traffic you’ve received.

'''Channel Status''' gives you an overview over the WAN link(s) your tunnel uses and tells you their names, whether they’re connected, disconnected or on standby, their IP addresses, their connection type (UDP, TCP, etc.), how long they’ve been running uninterruptedly, their latency and packet loss, and how much data traffic they’ve received and sent.

'''Traffic Monitor''' doesn’t work as of 18-11-2025 but is supposed to give you a visual live view of what your tunnel does.

== Tunnel ==
[[File:3a-essential-cloud-tunnel.png|none|500px]]
* Tunnel / QoS Preset: Allow to override the QoS preset for this tunnel. <Client Choice> will use the QoS preset configured on the client, <Custom QoS> will use the custom QoS rules configured on the server. Other choices are Bonding, Bonding (No Proxy), Packet Duplication, Seamless Failover, and Default QoS.
* Tunnel / Max Packet Size: The maximum packet size used for the tunnel protocol. This value must be the smalles MTU of all connected interfaces; it is only required to change in case automatic MTU detection fails.

== QoS ==
[[File:3b-essential-cloud-qos.png|none|500px]]

{| class="wikitable" style=max-width:75%
|+ General Rule Settings
|-
! Value !! Description
|-
| Priority || The priority of the rule. The higher the number, the bigger the slice of packets that this rule can process.
|-
| Duplication || Packet duplication factor for redundancy across multiple WAN links (0 = no duplication, 1 = full duplication).
|-
| Max. Bonding Latency || Maximum acceptable bonding latency in milliseconds for this traffic flow. This describes the difference between the best and the worst acceptable latency between interfaces.
|-
| Max. Downstream || Maximum downstream bandwidth allocation in Mbps for this rule.
|-
| Max. Upstream || Maximum upstream bandwidth allocation in Mbps for this rule.
|-
| Max. Channel || Maximum number of WAN channels that can be used for this traffic flow.
|-
| Channel Selection || Method for selecting WAN channels: Default uses standard bonding logic, Latency prioritizes lowest latency channels.
|-
| Bonding Proxy || Enable bonding proxy mode for this rule to handle connection state across multiple WAN links.
|-
| Distribution || Enable traffic distribution across multiple WAN links for load balancing.
|}

{| class="wikitable" style=max-width:75%
|+ Matching Rules
|-
! Value !! Description
|-
| Protocol || Network protocol to match for this QoS rule. Choose between Any, ICMP, TCP, UDP, TCP/UDP.
|-
| Source || Source IP address or network range (e.g. 192.168.1.0/24).
|-
| Source Port || Source port range or specific ports (e.g. 80,443 or 1000-2000).
|-
| Destination || Destination IP address or network range.
|-
| Destination Port || Source port range or specific ports.
|-
| DSCP || Differentiated Services Code Point for QoS marking (-1 = no marking).
|-
| Comment || Here, you can add a comment for this rule e.g. a short explanation of what it does if you have several rules in place that intricately complement each other.
|}

= Licenses =
[[File:4-licenses.png|none|500px]]
'''Licenses''' gives you an overview of all the licenses (NEITHER Bondix Essential Cloud related products NOR (future) license subscriptions!) you’ve tied to the email address with which you’re logged in. You can see how many tunnels they allow, whether they’re active or expired as well as how many days they’re valid in total and when they will end or have ended.

= Usage =
[[File:5-usage.jpg|none|500px]]
'''Usage''' shows you which servers you’re using with your tunnels (licenses or license subscriptions, NOT Bondix Essential Cloud!). They’re sorted by bonding throughput.

= Subscriptions =
[[File:6-subscriptions.jpg|none|500px]]
'''Subscriptions''' shows you all Bondix subscriptions (Bondix Essential Cloud and Bondix licenses subscriptions) that you’ve purchased using the email address with which you’re logged in.
'''Please note:''' You can only '''''view''''' your subscriptions here. If you want to '''''manage''''' them, you’ll need to login to your Bondix Webshop account at [[https://shop.bondix.de]].

= Resources =
[[File:7-resources.png|none|500px]]
'''Resources''' should be your first point of contact if you feel you need assistance with your Bondix solution. Feel free to explore our documentation which is constantly updated as well as our videos and FAQs. Installation Instructions help you get your system up and running for the first time.

= Download =
Download this manual here: [[https://226d8a3e-9b65-453b-93bd-7875e511be8d.usrfiles.com/ugd/226d8a_92c274eb9899421ba07cb220f0e5619c.pdf my.bondix.cloud Manual]] (English, PDF file, 1.3 MB]

Manuals/Server

2026-06-11T11:37:53Z

Sylvia:

[[Category:General]]

== Preparations ==
To install the Bondix server, you will need a few minutes of stable Internet, a web browser, and possibly some coffee or tea.

=== Supported Browsers ===
The following browsers have been tested to function properly with the Bondix server:
* Google Chrome
* MS Edge
* Mozilla Firefox

=== Updating the Bondix Server ===
If you want to update your Bondix server version, first delete the old installation scripts on your Linux VM by using the following command:

<nowiki>rm install-bondix-server.sh*</nowiki>

After that, just repeat the installation process as described above.

⚠️ '''This will NOT delete your server configuration! It will only delete the installation scripts and a recommended measure before updating your server.''' ⚠️

=== Installing the Linux VM (Ubuntu 20.4-26.04 LTS) ===
⚠️ '''For the installation, you will need root rights.''' ⚠️

Set your firewalls to the following settings:
Bondix server port shares
- TCP: 443, 80
- UDP: 44343
SSH (Optional): 22

Make sure your server has a public static IP and is reachable from the Internet.

Execute the following script in the terminal window of your server to download the latest version of the Bondix server:
<nowiki>wget https://releases.bondix.dev/endpoint/install-bondix-server.sh</nowiki>

<gallery widths="500" heights="300">
File:1-linux-install.png
</gallery>

To start the installation, enter the following commands:
<nowiki>chmod a+x install-bondix-server.sh
sudo ./install-bondix-server.sh</nowiki>

Confirm all the following prompts with the Enter key for a standard installation.

<gallery widths="500" heights="300">
File:2-linux-install.png
</gallery>

After completing the installation, you can reach the Bondix server web interface at the IP address shown. Log in with the username “admin” and the password previously generated during installation.

<gallery widths="300" heights="200">
File:3-login.png
</gallery>

== Bondix Server ==
=== Licensing ===
If your server is not already licensed, you first need to activate the Bondix Server Tunnel license under the menu item “Licensing”.

<gallery widths="500" heights="300" perrow="2">
File:4-nolicense.png
File:5-activate-license.png
</gallery>

Enter the Bondix license key here, as well as a valid email address to which the license key is bound. You can also enter a name for the server instance here. Then press “Submit”.

<gallery widths="300" heights="200">
File:6-license-key.png
</gallery>

After the successful activation, the Licensing overview will display the number of licensed tunnels as well as the expiry date of your active tunnel subscriptions with the respective expiry date and the maximum number of active server instances possible under this license number.

<gallery widths="500" heights="300">
File:7-successful-activation.png
</gallery>

You can add further additional tunnels/server instances at any time under the item “Activate License”.

=== Administration ===
==== Overview ====
This is the web interface of a licensed Bondix server.

<gallery widths="500" heights="500">
File:8-overview.png
</gallery>

==== Bondix Tunnels ====
To connect a Bondix-compatible router to a Bondix server, you first need to create a tunnel for this respective router. Only then does the server know that there will be a new router to receive data from and send data to.

===== Create a new tunnel =====
Navigate to the menu item “Tunnel”. Select the tunnel environment for which you want to create the tunnel by clicking the corresponding tab; the default is set to “env0”. Then, assign a unique tunnel name and press “Create”.

⚠️ '''The tunnel name must not contain any spaces.''' ⚠️

<gallery widths="500" heights="300" perrow="2">
File:9-add-tunnel.png
File:10-add-tunnel-detail.png
</gallery>

You will then automatically be navigated to the settings window of the newly created tunnel. There, set a password for establishing the connection, make sure that “Enabled” is ticked, and then press “Save”.

<gallery widths="500" heights="300">
File:11-tunnel-added.png
</gallery>

Your tunnel is now displayed under the menu item “Overview”. You can access settings for each tunnel simply by clicking on the tunnel name.

<gallery widths="500" heights="300">
File:12-tunnel-overview.png
</gallery>

===== Connect a compatible router to a Bondix server. =====
Make sure that the latest Bondix client is installed on your router. Go to the settings menu of your router’s Bondix client and enter the server’s IP address and the tunnel name and password you created in chapter 3.2.2 in the corresponding fields. Save your entry and then restart the service (Restart Service).

<gallery widths="500" heights="500">
File:13-tunnel-credentials.png
</gallery>

The tunnel is now listed in the Bondix server’s menu “Overview” including the number of its active connections. Click on the tunnel name to access the tunnel settings and options.

<gallery widths="500" heights="300">
File:12-tunnel-overview.png
</gallery>

===== Tunnel details and settings =====
====== Functions ======

<gallery widths="500" heights="500">
File:14-functions.png
</gallery>

{| class="wikitable"
! Function !! Effect
|-
| 1 Enabled || Activates (ticked) or deactivates (unticked) the tunnel.
|-
| 2 Revert || Undoes any changes that have not yet been saved.
|-
| 3 Save || Saves changes.
|-
| 4 Channel || Provides an overview of channels currently connected.
|}

''' Function “Override Client Settings” '''
If you activate this on server side, local tunnel presets and WAN priority settings of the connected router are overwritten or reset by the server’s settings. You will need to restart the tunnel.

<gallery widths="500" heights="300">
File:15-override-client-settings.png
</gallery>

====== Actions ======

<gallery widths="500" heights="500">
File:16-actions.png
</gallery>

{| class="wikitable"
! Function !! Effect
|-
| 1 Restart tunnel || Allows the tunnel connection to be disconnected briefly and then reconnected. This is needed for some changes to take effect.
|-
| 2 Open Monitor || Displays a graphical overview of the connections of the router.
|-
| 3 Expert Settings || Opens the server-side Bondix web monitor for diagnostic purposes.
|-
| 4 Delete Tunnel || Deletes a tunnel permanently without the possibility to restore it.
|}

===== Tunnel Environments =====
In Bondix, a tunnel environment is a pool of resources used by a group of tunnels. This includes packet cache, CPU core, a UDP listener, and a virtual network interface.

====== Add Environments ======
During the Bondix server installation, the software automatically creates a default environment with the name “env0”. You can create and add further environments via the menu item “Add Environment”.

<gallery widths="500" heights="300">
File:17-tunnel-environments.png
</gallery>

====== UDP Listener settings ======
For common scenarios, select “0.0.0.0 (Any Interface)” for the UDP Listener IP.

⚠️ '''Each environment must be assigned its own unique UDP Listener Port. This port must not be used elsewhere in the system, and it must not be blocked by a firewall.''' ⚠️

====== Virtual Interface settings ======
Leave the Virtual Interface Name blank to automatically generate a name for it.

⚠️ '''The Virtual Interface Name and the Virtual Network (CIDR) assigned to the Tunnel Environment must also be unique, not to be used in any other environment.''' ⚠️

====== Outgoing settings ======
The Outgoing Interface describes where you want to route your data traffic. Optionally, you can enter a specific Outgoing IP address.

====== Activate Tunnel-to-Tunnel Communication ======
The option “Disable traffic among routers” is activated by default due to Bondix providing multi-tenancy support. This feature prevents routers assigned to a Tunnel Environment from communicating with each other. If you deactivate “Disable traffic among routers”, routers in the same environment can interact. You can adjust this setting separately for each environment.

== Troubleshooting ==
Sometimes, your Bondix server may not work as expected. If that happens, you may find possible solutions in this section.
{| class="wikitable"
! Problem !! Solution
|-
| ? || Re-install Server (Update)
|-
| ? || Remove Server
|-
| ? || Start Bondix Service
|-
| ? || Stop Bondix Service
|-
| ? || Server update notification in Web interface update via console
|}

== Bondix Server Log ==
This is an exemplary overview of a server’s current log messages:

<gallery widths="500" heights="300">
File:18-server-log.png
</gallery>

Status

2026-06-11T11:37:33Z

Sylvia:

[[Category:Teltonika]]
[[Category:Manual]]
[[Category:General]]
=== Status ===
[[File:11-status-crop.png|center|border]]

==== Status information ====
In the Status Information, you can quickly see all facts to your Bondix Client, regarding your overall bonding as well as your individual channels.

{| class="wikitable"
! Value !! Description
|-
| Tunnel || Shows the name of your tunnel.
|-
| Status || Tells you whether your Bondix Client is connected at all.
|-
| Connected Channels || Gives you the number of WAN links currently active.
|-
| Client IP || Shows IP/DNS addresses.
|-
| Current Endpoint || Shows Bondix server’s IP/port.
|-
| Total Traffic || Shows total upload/download traffic.
|-
| Build Version || Shows which Bondix Client build you have installed.
|}

==== Channel Information ====
The Channel Information shows you which of your WAN links are available, connected and active, or faulty:

{| class="wikitable"
! Value !! Description
|-
| Name || Shows the name you assigned to the specific WAN link.
|-
| Status || Tells you whether the WAN link is connected, disables, or faulty.
|-
| Latency || Shows the WAN link’s current latency.
|-
| RX || Shows incoming traffic.
|-
| TX || Shows outgoing traffic.
|-
| Last Error || Displays the error message of a faulty WAN link.
|}

Monitor 7.02.x

2026-06-11T11:37:23Z

Sylvia:

[[Category:Manual]]
[[Category:Advanced Settings]]
[[Category:General]]
=== Monitor ===
[[File:7-advanced-settings-crop.png|center|border]]

With this release version, the local Bondix Web Monitor has been integrated in the Teltonika router menu. The monitor will enable you to have a look at the performance of your WAN links and configure their settings in real time. This is especially helpful if one of your WAN links does not perform as expected.
The monitor is only available if you’re connected to your router via HTTP. Due to technical reasons, the monitor will not show if you’re using HTTPS to connect to your router (e.g. via Teltonika RMS).

==== Setup ====
To set up the monitor, choose the following settings in the Advanced Settings section:
[[File:8-monitor-setup.png|center|border]]

{| class="wikitable"
! Field !! Value
|-
| Enable Monitor || On
|-
| Monitor HTTP Port || This port is set automatically.
|-
| Monitor API Key || This automatically generated API key is used to show the monitor in the Teltonika router’s Bondix menu.
|}

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

Layer 2

2026-06-11T11:37:11Z

Sylvia:

[[Category:Manual]]
[[Category:General]]
==== Layer 2 ====
With this option, you can set up a layer-2 tunnel directly with Bondix. A layer-2 tunnel is a virtual interface that is created on both client and server for each tunnel–packets coming in on one end will come out the other and vice versa. This is an advanced feature; further configuration must be done server-side depending on the usage scenario.
If you need more information on how to use layer 2 with your Teltonika router, please contact Teltonika directly.

[[File:9-layer2-crop.png|center|border]]

Advanced Settings

2026-06-11T11:37:00Z

Sylvia:

[[Category:General]]

==== Advanced Settings ====
Make sure to choose the following advanced settings for the Client on your Teltonika router:
[[File:7-advanced-settings-crop.png|center|border]]

{| class="wikitable"
! Field !! Value
|-
| Enable Bonding Proxy || On
Enable this proxy if you’re bonding connections with vastly different latencies (e.g. DSL and 5G/LTE), since it optimizes TCP connections and increases your overall throughput.
|-
| Maximum Packet Size || 1400
Change to lower setting if Bondix’ automatic MTU packet size detection fails.
|-
| Packet HMAC || Disabled
Set this value to “''SHA256''” only if you need tampering-proof data transfer since it reduces the general Bondix performance.
|-
| Verify Server Certificate || If required, a server certificate can be uploaded here.
Set option to “''on''” and browse for your CA file to upload.
|}

Interfaces

2026-06-11T11:36:48Z

Sylvia:

[[Category:WAN Interfaces]]
[[Category:Manual]]
[[Category:General]]
===== Interfaces =====
In this section, you can prioritize the use of WAN connections with two sets of options according to your needs.
[[File:5-interfaces.png|center|border]]

====== Preset ======
Every type of WAN link has different properties that make them suitable for different needs. You can configure them individually to ideally suit your use cases by choosing from 4 Interface presets:

{| class="wikitable"
! Preset !! Effect
|-
| Speed || The default setting that works for most scenarios.
|-
| Low Latency || Keeps latency as low as possible at the expense of bandwidth.
Often used for latency-sensitive scenarios, e.g. streaming.
|-
| Satellite || Mandatory setting for a high-latency WAN link (e.g. satellite).
⚠️ Does not apply to Starlink! ⚠️
|-
| TCP Mode || Useful if UDP traffic is expected to be problematic (e.g. UDP blocking by provider or local network). May cause higher base latency due to the nature of TCP.
|}

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

====== Priority ======
Per default, WAN connections are prioritized in using their available bandwidth according to their latency. Bondix usually prioritizes low-latency connections like Ethernet connections. The higher a connection’s latency gets, the lower Bondix sets its priority per default. In this section, you can set individual priorities for your WAN links by choosing from the following 4 options:
Default / High Priority / Higher Priority / Highest Priority

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

====== Up- / Downstream Limit ======
By design, Bondix normally finds the maximum bandwidth of a WAN link by continually evaluating data traffic generated by users over time. This can cause fluctuating bandwidths and/or increased buffering especially with, but not limited to, mobile connections. Setting a hard up- and/or downstream limit about 5% lower than the known maximum gives a base to work with, stabilizing and increasing the WAN link’s performance.

====== Example ======
You have 4 WAN links, 2 of which are 5G/LTE connections, and you only want to use those 2 evenly. To achieve that, you disable your 2 other WAN links, while giving your 2 mobile links the preset “''Speed''” and the priority “''Default''”:
[[File:6-example-crop.png|center|border]]

Tunnel Preset

2026-06-11T11:36:33Z

Sylvia:

[[Category:General]]
[[Category:WAN Interfaces]]
===== Tunnel Preset =====
[[File:4c-connection-code.png|center|border]]

{| class="wikitable"
! Preset !! Effect
|-
| Bonding || Ensures best performance in regards to bandwidth.
|-
| Packet Duplication || Used for scenarios where reliability is key: Each packet is sent with a copy.
Please choose this option wisely as it decreases bandwidth to a certain degree.
|-
| Packet Duplication 2x || Used for scenarios where reliability is key. Each packet is sent with two copies.
Please choose this option wisely as it decreases bandwidth to an even greater degree.
|-
| Satellite || Mandatory for scenarios where at least one of the bonded WAN links is a satellite connection.
⚠️ Does not apply to Starlink! ⚠️
|}

Configuration Mode

2026-06-11T11:36:14Z

Sylvia:

[[Category:General]]
[[Category:General Settings]]
===== Config Mode =====
The Config Mode is the method with which you want to enter your Bondix tunnel credentials. It can either be done manually, via certificate, or via Bondix quick connect code.

====== Manual ======
[[File:4a-manual-crop.png|center|border]]

{| class="wikitable"
! Field !! Value
|-
| Tunnel || Your tunnel’s name.
This is either part of the credentials you’ve received from your Bondix server provider, or the tunnel name you’ve created in your self-hosted Bondix server.
|-
| Password || Your password.
This is either part of the credentials you’ve received from your Bondix server provider, or the password you’ve created in your self-hosted Bondix server.
|-
| Server || Your server IP. This is either part of the credentials you’ve received from your Bondix server provider, or the IP address or host name of your self-hosted Bondix server.
|-
| Backup Server || A backup server acts as a fallback in case the server you’ve specified under “''Server''” in this section fails.
This is either part of the credentials you’ve received from your Bondix server provider, or the IP address or host name of your self-hosted Bondix backup server.
Otherwise, leave the field empty.
|}

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

====== Certificate ======
[[File:4b-certificate-crop.png|center|border]]

{| class="wikitable"
! Field !! Value
|-
| Tunnel Certificate || Browse for and upload the Tunnel Certificate which should be in PEM format.
|-
| Certificate Key || Browse for and upload the Certificate Key which should be in PEM format.
|-
| Server || Your server IP or host name.
|-
| Backup Server || Your backup server IP or host name.
|}

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

====== Connection Code ======
The Bondix connection code is an alphanumeric string that is used to automatically configure your tunnel connection. Just copy and paste.
[[File:4c-connection-code.png|center|border]]

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

General Teltonika Router Settings

2026-06-11T11:35:58Z

Sylvia:

[[Category:General]]
== General Router Settings ==
=== Load Balancing ===
Check that Teltonika Load Balancing functionality is deactivated on the router, as this would have a negative impact on Bondix performance and functionality.
[[File:2-load-balancing-crop.png|center|border]]

=== DNS ===
Ensure that you have configured DNS forwarding to a public server like 8.8.8.8 or 9.9.9.9 to receive DNS through the tunnel.
[[File:3-dns-filledin-crop.png|center|border]]

Manuals/Client

2026-06-11T11:35:35Z

Sylvia:

[[Category:General]]

This manual can be used for installing the Bondix Client on the following models:
* RUTX50
* RUTX12
* RUT950/955
* RUT360
* RUT240

== Preparations ==
To install the Bondix Client on your Teltonika router, you will need a few minutes of stable Internet, a web browser, and possibly some coffee or tea.

===Supported browsers===
The following browsers have been tested to function properly with Bondix:
*Google Chrome
*MS Edge
* Mozilla Firefox

===Teltonika Firmware===
Bondix Clients are available for many Teltonika firmware versions. In order to fully benefit from all new features to their full extend though, we recommend you update your Teltonika router model to its latest Teltonika stable firmware at the [https://wiki.teltonika-networks.com/view/Main_Page|Teltonika Knowledge Base].

==Client Installation==

{{Colored_box|Text=We strongly recommend you reset all router settings before starting the installation.}}

Visit [https://www.bondixintelligence.com/releases|https://www.bondixintelligence.com/releases - Teltonika] and download the ''.TAR.GZ'' file matching your Teltonika router’s firmware version.

To install the Bondix Client, you will need administration rights on your Teltonika router. For that, make sure you have chosen the option “''Advanced''” in the section “''System''” › “''Administration''” › “''General Settings''” › “''Configuration Mode''”.
[[File:0-admin-rights-crop.png|center|border]]

Open your Teltonika router menu, navigate to the menu item “''Services''” › “''Package Manager''” › “''Upload''”. Click on “''Browse''”, choose the file you just downloaded to upload it to the router, and then press “''Install Package''”.
[[File:1-package-manager-upload-crop.png|center|border]]

{{Colored_box|Text=There will be a package verification popup dialogue telling you the Bondix Client is an unauthorized package.
Click on “''proceed''” to continue with the installation.}}

Also, there will be a popup dialogue telling you that the package installation needs a reboot. Click on “''Reboot''” to finish the installation. If this prompt doesn’t appear which may happen due to technical issues, reload your Teltonika router’s web interface (''STRG+F5 / Command+R'') and reboot manually (“''System''” › “''Reboot''”).

If the Bondix Client was installed correctly, you’ll find a new menu item “''Bondix''” in the section “''Network''” of your Teltonika router.

==General Router Settings==
=== Load Balancing===
Check that Teltonika Load Balancing functionality is deactivated on the router, as this would have a negative impact on Bondix performance and functionality.
[[File:2-load-balancing-crop.png|center|border]]

===DNS===
Ensure that you have configured DNS forwarding to a public server like 8.8.8.8 or 9.9.9.9 to receive DNS through the tunnel.
[[File:3-dns-filledin-crop.png|center|border]]

==Bondix Settings==
=== Settings===
====General Settings====
In the general settings for the Bondix Client, you’ll be able to configure your tunnel via different modes of configuration:
[[File:4-general-settings-crop.png|center|border]]

=====Config Mode=====
The Config Mode is the method with which you want to enter your Bondix tunnel credentials. It can either be done manually, via certificate, or via Bondix connection code.

======Manual ======
[[File:4a-manual-crop.png|center|border]]

{| class="wikitable"
!Field!!Value
|-
|Tunnel ||Your tunnel’s name.
This is either part of the credentials you’ve received from your Bondix server provider, or the tunnel name you’ve created in your self-hosted Bondix server.
|-
|Password||Your password.
This is either part of the credentials you’ve received from your Bondix server provider, or the password you’ve created in your self-hosted Bondix server.
|-
|Server ||Your server IP. This is either part of the credentials you’ve received from your Bondix server provider, or the IP address or host name of your self-hosted Bondix server.
|-
|Backup Server ||A backup server acts as a fallback in case the server you’ve specified under “''Server''” in this section fails.
This is either part of the credentials you’ve received from your Bondix server provider, or the IP address or host name of your self-hosted Bondix backup server.
Otherwise, leave the field empty.
|}

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

======Certificate======
[[File:4b-certificate-crop.png|center|border]]

{| class="wikitable"
!Field!!Value
|-
|Tunnel Certificate||Browse for and upload the Tunnel Certificate which should be in PEM format.
|-
|Certificate Key|| Browse for and upload the Certificate Key which should be in PEM format.
|-
|Server ||Your server IP or host name.
|-
|Backup Server ||Your backup server IP or host name.
|}

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

======Connection Code======
The Bondix connection code is an alphanumeric string that is used to automatically configure your tunnel connection. Just copy and paste.
[[File:4c-connection-code.png|center|border]]

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

====WAN Interfaces====
In this section, you can prioritize the use WAN connections with two sets of options according to your needs.

=====Tunnel Preset =====
{| class="wikitable"
!Preset !!Effect
|-
|Bonding||Ensures best performance in regards to bandwidth.
|-
|Packet Duplication||Used for scenarios where reliability is key: Each packet is sent with a copy.
Please choose this option wisely as it decreases bandwidth to a certain degree.
|-
|Packet Duplication 2x||Used for scenarios where reliability is key. Each packet is sent with two copies.
Please choose this option wisely as it decreases bandwidth to an even greater degree.
|-
|Satellite||Mandatory for scenarios where at least one of the bonded WAN links is a satellite connection.
⚠️ Does not apply to Starlink! ⚠️
|}

[[Tunnel Preset]]

=====Interfaces=====
In this section, you can prioritize the use of WAN connections with two sets of options according to your needs.
[[File:5-interfaces.png|center|border]]

======Preset ======
Every type of WAN link has different properties that make them suitable for different needs. You can configure them individually to ideally suit your use cases by choosing from 4 Interface presets:

{| class="wikitable"
!Preset !!Effect
|-
|Speed||The default setting that works for most scenarios.
|-
|Low Latency||Keeps latency as low as possible at the expense of bandwidth.
Often used for latency-sensitive scenarios, e.g. streaming.
|-
|Satellite||Mandatory setting for a high-latency WAN link (e.g. satellite).
⚠️ Does not apply to Starlink! ⚠️
|-
|TCP Mode||Useful if UDP traffic is expected to be problematic (e.g. UDP blocking by provider or local network). May cause higher base latency due to the nature of TCP.
|}

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

======Priority======
Per default, WAN connections are prioritized in using their available bandwidth according to their latency. Bondix usually prioritizes low-latency connections like Ethernet connections. The higher a connection’s latency gets, the lower Bondix sets its priority per default. In this section, you can set individual priorities for your WAN links by choosing from the following 4 options:
Default / High Priority / Higher Priority / Highest Priority

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

======Up- / Downstream Limit======
By design, Bondix normally finds the maximum bandwidth of a WAN link by continually evaluating data traffic generated by users over time. This can cause fluctuating bandwidths and/or increased buffering especially with, but not limited to, mobile connections. Setting a hard up- and/or downstream limit about 5% lower than the known maximum gives Bondix a base to work with, stabilizing and increasing the WAN link’s performance.

======Example======
You have 4 WAN links, 2 of which are 5G/LTE connections, and you only want to use those 2 evenly. To achieve that, you disable your 2 other WAN links, while giving your 2 mobile links the preset “''Speed''” and the priority “''Default''”:
[[File:6-example-crop.png|center|border]]

====Advanced Settings====
Make sure to choose the following advanced settings for the Bondix Client on your Teltonika router:
[[File:7-advanced-settings-crop.png|center|border]]

{| class="wikitable"
!Field!!Value
|-
|Enable Bonding Proxy||On
Enable this proxy if you’re bonding connections with vastly different latencies (e.g. DSL and 5G/LTE), since it optimizes TCP connections and increases your overall throughput.
|-
|Maximum Packet Size||1400
Change to lower setting if Bondix’s automatic MTU packet size detection fails.
|-
|Packet HMAC||Disabled
Set this value to “''SHA256''” only if you need tampering-proof data transfer since it reduces the general Bondix performance.
|-
|Verify Server Certificate||If required, a server certificate can be uploaded here.
Set option to “''on''” and browse for your CA file to upload.
|}

====Layer 2====
With this option, you can set up a layer-2 tunnel directly with Bondix. A layer-2 tunnel is a virtual interface that is created on both client and server for each tunnel–packets coming in on one end will come out the other and vice versa. This is an advanced feature; further configuration must be done server-side depending on the usage scenario.
If you need more information on how to use layer 2 with your Teltonika router, please contact Teltonika directly.

[[File:9-layer2-crop.png|center|border]]

===Monitor===
With this release version, the local Bondix Web Monitor has been integrated in the Teltonika router menu. The monitor will enable you to have a look at the performance of your WAN links and configure their settings in real time. This is especially helpful if one of your WAN links does not perform as expected.
The monitor is only available if you’re connected to your router via HTTP. Due to technical reasons, the monitor will not show if you’re using HTTPS to connect to your router (e.g. via Teltonika RMS).

====Setup====
To set up the monitor, choose the following settings in the Advanced Settings section:
[[File:8-monitor-setup.png|center|border]]

{| class="wikitable"
!Field!!Value
|-
|Enable Monitor||On
|-
|Monitor HTTP Port||This port is set automatically.
|-
|Monitor API Key|| This automatically generated API key is used to show the monitor in the Teltonika router’s Bondix menu.
|}

{{Colored_box|Text=To save your changes, always click on “''Save and Apply''”, then “''Restart Service''”.}}

[[Monitor 7.02.x]]

====Traffic Monitor====
Clicking on the “''Monitor''” link in your Teltonika router’s Bondix menu will give you a graphical overview of the data traffic and the connection status of your tunnel’s connected WAN links:
[[File:10-monitor-crop.png|center|border]]

=====Global =====
{| class="wikitable"
!Value!!Description
|-
|Queued Items||Packets that have been received locally but haven’t been sent yet.
|-
|Packet Buffer ||Total amount of packets in cache.
|-
|Used Channel||Number of active channels.
|}

=====Channel=====
{| class="wikitable"
!Value!!Description
|-
|TX Out || Number of outgoing traffic packets.
|-
|TX Lost||Number of lost outgoing traffic packets.
|-
|RX In||Number of incoming traffic packets.
|-
|RX Lost||Number of lost incoming traffic packets.
|-
|In Transit||Packets that have been sent but not acknowledged yet.
|-
|Latency||Latency in ms.
|-
|TX Loss % (sec)||Measured outgoing packet loss over the last second.
|-
|TX Loss % (min)||Measured outgoing packet loss over the last minute.
|-
|Capacity||Number of packets that can be sent out through the channel.
|}

===Status ===
[[File:11-status-crop.png|center|border]]

====Status information====
In the Status Information, you can quickly see all facts to your Bondix Client, regarding your overall bonding as well as your individual channels.

{| class="wikitable"
!Value!!Description
|-
|Tunnel ||Shows the name of your tunnel.
|-
|Status ||Tells you whether your Bondix Client is connected at all.
|-
|Connected Channels||Gives you the number of WAN links currently active.
|-
|Client IP||Shows IP/DNS addresses.
|-
|Current Endpoint||Shows Bondix server’s IP/port.
|-
|Total Traffic||Shows total upload/download traffic.
|-
|Build Version||Shows which Bondix Client build you have installed.
|}

====Channel Information====
The Channel Information shows you which of your WAN links are available, connected and active, or faulty:

{| class="wikitable"
!Value!!Description
|-
|Name
|Shows the name you assigned to the specific WAN link.
|-
|Status ||Tells you whether the WAN link is connected, disables, or faulty.
|-
|Latency||Shows the WAN link’s current latency.
|-
|RX||Shows incoming traffic.
|-
|TX||Shows outgoing traffic.
|-
|Last Error||Displays the error message of a faulty WAN link.
|}

==Download==
Download this manual as PDF file here: []

Server

2026-06-11T11:34:59Z

Sylvia:

[[Category:Server]]
[[Category:General]]
[[Main_Page|Start]] > [[Main_Page#Marketing_Material|Marketing Material]] > [[Manuals|Manuals]] > [[Manuals/Sane-server-v01|Bondix Server v01]]

== Preparations ==
To install the Bondix S Server, you will need a few minutes of stable Internet, a web browser, and possibly some coffee or tea.

=== Supported Browsers ===
The following browsers have been tested to function properly with the Bondix server:
* Google Chrome
* MS Edge
* Mozilla Firefox

=== Updating the Bondix Server ===
If you want to update your Bondix server version, first delete the old installation scripts on your Linux VM by using the following command:

<nowiki>rm install-bondix-server.sh*</nowiki>

After that, just repeat the installation process as described above.

⚠️ '''This will NOT delete your server configuration! It will only delete the installation scripts and a recommended measure before updating your server.''' ⚠️

=== Installing the Linux VM (Ubuntu 20.4-24.04) ===
⚠️ '''For the installation, you will need root rights.''' ⚠️

Set your firewalls to the following settings:
<nowiki>Bondix server port shares
- TCP: 443, 80
- UDP: 44343
SSH (Optional): 22</nowiki>

Make sure your server has a public static IP and is reachable from the Internet.

Execute the following script in the terminal window of your server to download the latest version of the Bondix server:
<nowiki>wget https://releases.bondix.dev/endpoint/install-bondix-server.sh</nowiki>

<gallery widths="500" heights="300">
File:1-linux-install.png
</gallery>

To start the installation, enter the following commands:
<nowiki>chmod a+x install-bondix-server.sh
sudo ./install-bondix-server.sh</nowiki>

Confirm all the following prompts with the Enter key for a standard installation.

<gallery widths="500" heights="300">
File:2-linux-install.png
</gallery>

After completing the installation, you can reach the Bondix server web interface at the IP address shown. Log in with the username “admin” and the password previously generated during installation.

<gallery widths="300" heights="200">
File:3-login.png
</gallery>

== Bondix Server ==
=== Licensing ===
If your server is not already licensed, you first need to activate the Bondix Server Tunnel license under the menu item “Licensing”.

<gallery widths="500" heights="300" perrow="2">
File:4-nolicense.png
File:5-activate-license.png
</gallery>

Enter the Bondix license key here, as well as a valid email address to which the license key is bound. You can also enter a name for the server instance here. Then press “Submit”.

<gallery widths="300" heights="200">
File:6-license-key.png
</gallery>

After the successful activation, the Licensing overview will display the number of licensed tunnels as well as the expiry date of your active tunnel subscriptions with the respective expiry date and the maximum number of active server instances possible under this license number.

<gallery widths="500" heights="300">
File:7-successful-activation.png
</gallery>

You can add further additional tunnels/server instances at any time under the item “Activate License”.

=== Administration ===
==== Overview ====
This is the web interface of a licensed Bondix server.

<gallery widths="500" heights="500">
File:8-overview.png
</gallery>

==== Bondix Tunnels ====
To connect a Bondix-compatible router to a Bondix server, you first need to create a tunnel for this respective router. Only then does the server know that there will be a new router to receive data from and send data to.

===== Create a new Bondix tunnel =====
Navigate to the menu item “Tunnel”. Select the tunnel environment for which you want to create the tunnel by clicking the corresponding tab; the default is set to “env0”. Then, assign a unique tunnel name and press “Create”.

⚠️ '''The tunnel name must not contain any spaces.''' ⚠️

<gallery widths="500" heights="300" perrow="2">
File:9-add-tunnel.png
File:10-add-tunnel-detail.png
</gallery>

You will then automatically be navigated to the settings window of the newly created tunnel. There, set a password for establishing the connection, make sure that “Enabled” is ticked, and then press “Save”.

<gallery widths="500" heights="300">
File:11-tunnel-added.png
</gallery>

Your tunnel is now displayed under the menu item “Overview”. You can access settings for each tunnel simply by clicking on the tunnel name.

<gallery widths="500" heights="300">
File:12-tunnel-overview.png
</gallery>

===== Connect a compatible router to a Bondix server. =====
Make sure that the latest Bondix client is installed on your router. Go to the settings menu of your router’s Bondix client and enter the server’s IP address and the tunnel name and password you created in chapter 3.2.2 in the corresponding fields. Save your entry and then restart the service (Restart Service).

<gallery widths="500" heights="500">
File:13-tunnel-credentials.png
</gallery>

The tunnel is now listed in the Bondix server’s menu “Overview” including the number of its active connections. Click on the tunnel name to access the tunnel settings and options.

<gallery widths="500" heights="300">
File:12-tunnel-overview.png
</gallery>

===== Tunnel details and settings =====
====== Functions ======

<gallery widths="500" heights="500">
File:14-functions.png
</gallery>

{| class="wikitable"
! Function !! Effect
|-
| 1 Enabled || Activates (ticked) or deactivates (unticked) the tunnel.
|-
| 2 Revert || Undoes any changes that have not yet been saved.
|-
| 3 Save || Saves changes.
|-
| 4 Channel || Provides an overview of channels currently connected.
|}

''' Function “Override Client Settings” '''
If you activate this on server side, local tunnel presets and WAN priority settings of the connected router are overwritten or reset by the server’s settings. You will need to restart the tunnel.

<gallery widths="500" heights="300">
File:15-override-client-settings.png
</gallery>

====== Actions ======

<gallery widths="500" heights="500">
File:16-actions.png
</gallery>

{| class="wikitable"
! Function !! Effect
|-
| 1 Restart tunnel || Allows the tunnel connection to be disconnected briefly and then reconnected. This is needed for some changes to take effect.
|-
| 2 Open Monitor || Displays a graphical overview of the connections of the router.
|-
| 3 Expert Settings || Opens the server-side Bondix web monitor for diagnostic purposes.
|-
| 4 Delete Tunnel || Deletes a tunnel permanently without the possibility to restore it.
|}

===== Tunnel Environments =====
In the Bondix server, a tunnel environment is a pool of resources used by a group of tunnels. This includes packet cache, CPU core, a UDP listener, and a virtual network interface.

====== Add Environments ======
During the Bondix server installation, the software automatically creates a default environment with the name “env0”. You can create and add further environments via the menu item “Add Environment”.

<gallery widths="500" heights="300">
File:17-tunnel-environments.png
</gallery>

====== UDP Listener settings ======
For common scenarios, select “0.0.0.0 (Any Interface)” for the UDP Listener IP.

⚠️ '''Each environment must be assigned its own unique UDP Listener Port. This port must not be used elsewhere in the system, and it must not be blocked by a firewall.''' ⚠️

====== Virtual Interface settings ======
Leave the Virtual Interface Name blank to automatically generate a name for it.

⚠️ '''The Virtual Interface Name and the Virtual Network (CIDR) assigned to the Tunnel Environment must also be unique, not to be used in any other environment.''' ⚠️

====== Outgoing settings ======
The Outgoing Interface describes where you want to route your data traffic. Optionally, you can enter a specific Outgoing IP address.

====== Activate Tunnel-to-Tunnel Communication ======
The option “Disable traffic among routers” is activated by default due to Bondix providing multi-tenancy support. This feature prevents routers assigned to a Tunnel Environment from communicating with each other. If you deactivate “Disable traffic among routers”, routers in the same environment can interact. You can adjust this setting separately for each environment.

== Troubleshooting ==
Sometimes, your Bondix server may not not work as expected. If that happens, you may find possible solutions in this section.
{| class="wikitable"
! Problem !! Solution
|-
| ? || Re-install Server (Update)
|-
| ? || Remove Server
|-
| ? || Start Bondix Service
|-
| ? || Stop Bondix Service
|-
| ? || Server update notification in Web interface update via console
|}

== Bondix Server Log ==
This is an exemplary overview of a server’s current log messages:

<gallery widths="500" heights="300">
File:18-server-log.png
</gallery>

== Download ==
Download this manual as a PDF file from here: [https://bondixintelligence.sharepoint.com/:b:/s/BondixIntelligenceCoreTeam/ETzIJiPTEnFNkHPDsR_Fa54BUefrowdEGuaKzl_QR2PH2w?e=iTGhiP bondix_server_manual_v1_202202.pdf]

Client Installation

2026-06-11T11:34:40Z

Sylvia:

[[Category:General]]
[[Category:7.02.x]]
== Client Installation ==

{{Colored_box|Text=We strongly recommend you reset all router settings before starting the installation.}}

Visit [https://www.bondixintelligence.com/releases|https://www.bondixintelligence.com/releases - Teltonika] and download the ''.TAR.GZ'' file matching your Teltonika router’s firmware version.

To install the Bondix Client, you will need administration rights on your Teltonika router. For that, make sure you have chosen the option “''Advanced''” in the section “''System''” › “''Administration''” › “''General Settings''” › “''Configuration Mode''”.
[[File:0-admin-rights-crop.png|center|border]]

Open your Teltonika router menu, navigate to the menu item “''Services''” › “''Package Manager''” › “''Upload''”. Click on “''Browse''”, choose the file you just downloaded to upload it to the router, and then press “''Install Package''”.
[[File:1-package-manager-upload-crop.png|center|border]]

{{Colored_box|Text=There will be a package verification popup dialogue telling you the Bondix Client is an unauthorized package.
Click on “''proceed''” to continue with the installation.}}

Also, there will be a popup dialogue telling you that the package installation needs a reboot. Click on “''Reboot''” to finish the installation. If this prompt doesn’t appear which may happen due to technical issues, reload your Teltonika router’s web interface (''STRG+F5 / Command+R'') and reboot manually (“''System''” › “''Reboot''”).

If the Bondix Client was installed correctly, you’ll find a new menu item “''Bondix''” in the section “''Network''” of your Teltonika router.

Downloads

2026-06-11T11:33:44Z

Sylvia:

= Bondix Software Downloads =

This page provides download links for Bondix software compatible with various devices and firmware versions. Select the appropriate file based on your device model and firmware version.

'''Current Release Version:''' 1.26.01.x''' '''
{{Colored_box|Text=By initiating the download of the software from this site, you hereby acknowledge and consent to be bound by the terms of our [https://www.bondixintelligence.com/_files/ugd/226d8a_e5e6dbbc57124ed985bad80fa49ccbc8.pdf End User License Agreement (EULA)] and Terms of Use, which constitute a legally binding contract between you and SIMA GmbH.

Please review these documents carefully prior to downloading.}}

==Client==

{{Colored_box|Text=Please make sure to '''EXACTLY match your RUTOS''' version when downloading your Bondix client.

Example: If your router is updated to 07.22.1, our Bondix version 1.26.01.2/07.22 is '''NOT the correct version''' and you need to '''DOWNGRADE''' your router to 07.22 to be able to use Bondix.}}

===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!1.25.7.6/07.20.3 (Prev)
!1.26.01.3/07.22.3 (Stable)
!1.26.01.3/07.23.5 (Latest)
|-

|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTX_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTX_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTX_R_00.07.23.5.tar.gz Download]
|-
|RUTM
|RUTM09, RUTM10, RUTM11, RUTM16, RUTM20, RUTM30, RUTM31, RUTM50, RUTM51, RUTM52, RUTM54, RUTM55, RUTM56, RUTM59
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTM_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTM_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTM_R_00.07.23.5.tar.gz Download]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956, RUT976, RUT981, RUT986
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT9M_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT9M_R_00.07.23.5.tar.gz Download]
|-
|RUT2M
|RUT200, RUT202, RUT204, RUT206, RUT241, RUT260, RUT271, RUT276, RUT281
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT2M_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT2M_R_00.07.23.5.tar.gz Download]
|-
|RUTC
|RUTC40, RUTC41, RUTC42, RUTC50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTC_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTC_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTC_R_00.07.23.5.tar.gz Download]
|-
|RUTE
|RUT206, RUT271
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTE_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTE_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTE_R_00.07.23.5.tar.gz Download]
|-
|OTD5
|OTD500
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-OTD5_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-OTD5_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-OTD5_R_00.07.23.5.tar.gz Download]
|-
|ATRM50
|ATRM50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-ATRM50_R_00.07.20.3.tar.gz Download]
|-
|ALTOS
|ALTOS
|colspan="3"| Coming soon
|}

====EOL====
For routers designated as [https://teltonika-networks.com/support/eol-products "End of Production"] by Teltonika Networks, we no longer provide updated Bondix Client versions. If your device is marked as EOL and you require further support or newer versions, please contact us directly via email.

==Server==

===Latest Version (1.26.01.2)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.26.01.2.sh install-bondix-server-1.26.01.2.sh]

===Stable Version (1.25.7.6)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.25.7.6.sh install-bondix-server-1.25.7.6.sh]

Proceed to [[Manuals/Server| Installing a Bondix Server]].

[[Category:General]]

Howto essential

2026-06-11T11:33:21Z

Sylvia:

=== How to start with the Bondix Essential Cloud service ===

==== Installing the Teltonika Bondix client ====
You can find the latest Bondix client for your Teltonika device on our website at:

[[Downloads#Teltonika Routers]]

[[File:Mh65.png|center|frameless|902x902px]]

Please download the client which matches your device and RutOS version.

'''- IMPORTANT!:'''

Please note that the Bondix client is only working with its specific RutOS Version. For example, if you run a Teltonika device with RutOS 7.16. you will need to upgrade to 7.16.3 to use the Bondix client.

This can sometimes also include the need to downgrade a Teltonikas RutOS to a matching version, in advance to the Bondix client installation.

'''-'''

After you downloaded the matching client, use the Teltonika package manager in the System menu to install the Bondix client
[[File:Grafik11.png|center|frameless|1002x1002px]]

and confirm the installation:
[[File:Bgbf65.png|center|frameless|757x757px]]

After you proceeded the following reboot, you will find the Bondix client in the Network menu of your Teltonika device.

==== Preparing DNS ====
For proper internet access while the Bondix tunnel is used, your Teltonika router will need a dedicated DNS server configuration besides the server addresses your router may obtain from the used carriers.

To configure this server, just use the Network DNS menu of your Teltonika device to add DNS servers of your choice (in our example, Google DNS).
[[File:Gra44.png|center|frameless|954x954px]]
==== Setting up the Bondix tunnel ====
After the successful subscription to the '''Bondix Essential Cloud''' service, you will receive an email with your Bondix tunnel credentials. For a speedy start, the most relevant information in the email is your unique '''Bondix QuickConnect code'''.
[[File:Ccf.png|center|frameless|544x544px]]
To start, just copy this code from your email and enter it in the '''QuickConnect code''' menu of your Teltonika’s Bondix client:
[[File:Dd53.png|center|thumb|1152x1152px]]
then switch the Enabled button to active and press the '''Save configuration''' button.

==== And that´s it ====
[[File:Gk65.png|center|frameless|1400x1400px]]

[[Category:General]]

Main Page

2026-06-11T11:33:07Z

Sylvia:

{{DISPLAYTITLE:Start}}

== Welcome! ==

This is the Bondix Wiki, our ever-growing knowledge base. Here, we collect all things Bondix. We offer handy quick-start information but also in-depth how-tos for installation, debugging, and general understanding, as well as pretty-looking and informative marketing material.

Feel free to roam around and take all the wisdom you need to bring your Bondix knowledge and understanding to the next level.

== Get Started ==

This section helps you get your Bondix system up and running in no time.

=== Bondix Hosted Essential ===

#[[Howto essential|Bondix Hosted Essential How-To]] Setup Bondix Hosted Essential on your Teltonika device.

=== Classic Bondix Installation ===
# <big>'''[[Downloads|Download the latest release versions]]'''</big> Download the latest Bondix software suitable for your device and see changelogs and release notes. Download & installation are free-of-charge for all of our software.
# [[Client Installation|Bondix Client Installation]] Install Bondix on your Teltonika device.
# [[Server|Bondix Server Installation]] Install and configure your Bondix server.

{{Colored_box|Text=Bondix Licenses have a fixed start and end date and cannot be renewed. If they expire, you need to purchase a new Bondix license code and insert it into your server the same way you did the first time: [[Server|Bondix Server Installation]]!}}

=== Bondix CloudLink Bundle ===

If you want to get your '''Bondix CloudLink Bundle''' up and running, our partner [https://www.unwirednetworks.com Unwired Networks] has a detailed step-by-step manual for that: [https://docs.unwirednetworks.com/docs/cloudlink/teltonika_cloudlink.html Bondix CloudLink]

{{Colored_box|Text=If you need technical assistance, please open up a support ticket in our [https://support.bondix.net/ Bondix Support Portal]!}}
=== Manuals ===
In our manuals, you can find more detailed information on different settings and values that can cater to special circumstances, environments, and needs. They are updated continually, so screenshots may vary. The overall system is the same.
* [[Manuals/Client|Bondix on Teltonika devices]]
** [[Client Installation]]
** [[General Teltonika Router Settings]]
** [[Configuration Mode]]
** [[Tunnel Preset]]
** [[Interfaces]]
** [[Advanced Settings]]
** [[Layer 2]]
** [[Monitor 7.02.x]]
** [[Status]]
* [[Manuals/Server|Bondix Server Setup]]
** [https://docs.unwirednetworks.com/docs/cloudlink/teltonika_cloudlink.html Bondix CloudLink]
** [[my.bondix.cloud]]
* [[Manuals/Webshop|How to order Bondix in the Bondix Webshop]]

== General Information ==
This section gives you information on what Bondix is and how it works. Also, it's where we collect FAQs and especially their answers.
* [[Architecture]]
* [[Licenses]]
* [[FAQs]]

== Deep-dive Topics ==
In this section, you'll find specialized knowledge that is very technical and/or serves as a how-to for special use cases.
=== Client and Server ===
* [[Transparent Bonding Proxy]]
* [[Teltonika Portforwarding|General port forwarding]]
* [[Quality of Service]]
* [[Layer2]]
* [[Presets]]
* [[QuickConnect]]
* [[DMZ and 1:1 NAT configuration]]

=== Client ===
* [[Client/StaticRoutes|How to create static routes]]
* [[Teltonika Portforwarding|How to create a port-forward with Teltonika Routers]]
* [[Starlink|Bondix and Starlink]]
* [[Client]]
* [[Client/OpenWRT]]
* [[Client/RUTX12]]
* [[Client Configuration]]

=== Server ===
* [[Certificates|How to setup certificate-based authorization]]
* [[Server Capacity|How to calculate how many Bondix Servers you need]]
* [[Server Licensing|How to add licenses to your Bondix Server]]
* [[Server/Access Control]]
* [[Server/Changing Ports]]
* [[Server/Configuration]]
* [[Server/Routes]]
* [[Server Certificates with LetsEncrypt]]
* [[Server Configuration]]

== Marketing Material ==
Here, you can find all marketing material we have to share in one place.

===== Basic Product Info =====
[[File:Bondix-product-info-2024.pdf|thumb]]
[[File:Bondix-product-info-2024-de.pdf|thumb]]

Product images
<gallery>
Bondix-product-license-trial-web.png|Product image Trial license
Bondix-product-license-iot-web.png|Product image IoT license
Bondix-product-license-standard-web.png|Product image Standard license
Bondix-product-license-enterprise-web.png|Product image Enterprise license
Bondix-product-license-ultimate-web.png|Product image Ultimate license
</gallery>

===== Presentations =====
'''Generic'''

[[File:Presentation-bondix-wan-bonding-generic-202308.pdf|thumb|What is WAN Bonding?]] 
[[File:Presentation-bondix-licensing-202309.pdf|thumb|Bondix licensing in a tiny nutshell]]

'''Teltonika-specific'''

[[File:Bondix-webinar-dec2022-web2.pdf|thumb|Joint webinar Bondix and Teltonika, Dec 2022]] -->
[https://youtu.be/GSKhc_qOp1o YouTube - Paving New Bonding Possibilities in IIoT]

[[Category:General]]

Downloads

2026-06-11T11:25:53Z

Sylvia: /* Packages */

Downloads

2026-06-11T11:20:30Z

Sylvia: /* Packages */

= Bondix Software Downloads =

This page provides download links for Bondix software compatible with various devices and firmware versions. Select the appropriate file based on your device model and firmware version.

'''Current Release Version:''' 1.26.01.x''' '''
{{Colored_box|Text=By initiating the download of the software from this site, you hereby acknowledge and consent to be bound by the terms of our [https://www.bondixintelligence.com/_files/ugd/226d8a_e5e6dbbc57124ed985bad80fa49ccbc8.pdf End User License Agreement (EULA)] and Terms of Use, which constitute a legally binding contract between you and SIMA GmbH.

Please review these documents carefully prior to downloading.}}

==Client==

{{Colored_box|Text=Please make sure to '''EXACTLY match your RUTOS''' version when downloading your Bondix client.

Example: If your router is updated to 07.22.1, our Bondix version 1.26.01.2/07.22 is '''NOT the correct version''' and you need to '''DOWNGRADE''' your router to 07.22 to be able to use Bondix.}}

===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!1.25.7.6/07.20.3 (Prev)
!1.26.01.3/07.22.3 (Stable)
!1.26.01.3/07.23.5 (Latest)
|-

|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTX_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTX_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTX_R_00.07.23.5.tar.gz Download]
|-
|RUTM
|RUTM09, RUTM10, RUTM11, RUTM16, RUTM20, RUTM30, RUTM31, RUTM50, RUTM51, RUTM52, RUTM54, RUTM55, RUTM56, RUTM59
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTM_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTM_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTM_R_00.07.23.5.tar.gz Download]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956, RUT976, RUT981, RUT986
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT9M_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT9M_R_00.07.23.5.tar.gz Download]
|-
|RUT2M
|RUT200, RUT202, RUT204, RUT206, RUT241, RUT260, RUT271, RUT276, RUT281
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT2M_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT2M_R_00.07.23.5.tar.gz Download]
|-
|RUTC
|RUTC40, RUTC41, RUTC42, RUTC50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTC_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTC_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTC_R_00.07.23.5.tar.gz Download]
|-
|RUTE
|RUT206, RUT271
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTE_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTE_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTE_R_00.07.23.5.tar.gz Download]
|-
|OTD5
|OTD500
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-OTD5_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-OTD5_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-OTD5_R_00.07.23.5.tar.gz Download]
|-
|ATRM50
|ATRM50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-ATRM50_R_00.07.20.3.tar.gz Download]
|-
|ALTOS
|ALTOS
|
| Coming soon
|
|}

====EOL====
For routers designated as [https://teltonika-networks.com/support/eol-products "End of Production"] by Teltonika Networks, we no longer provide updated Bondix Client versions. If your device is marked as EOL and you require further support or newer versions, please contact us directly via email.

==Server==

===Latest Version (1.26.01.2)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.26.01.2.sh install-bondix-server-1.26.01.2.sh]

===Stable Version (1.25.7.6)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.25.7.6.sh install-bondix-server-1.25.7.6.sh]

Proceed to [[Manuals/Server| Installing a Bondix Server]].

Downloads

2026-06-11T11:18:20Z

Sylvia: /* Teltonika Routers */

= Bondix Software Downloads =

This page provides download links for Bondix software compatible with various devices and firmware versions. Select the appropriate file based on your device model and firmware version.

'''Current Release Version:''' 1.26.01.x''' '''
{{Colored_box|Text=By initiating the download of the software from this site, you hereby acknowledge and consent to be bound by the terms of our [https://www.bondixintelligence.com/_files/ugd/226d8a_e5e6dbbc57124ed985bad80fa49ccbc8.pdf End User License Agreement (EULA)] and Terms of Use, which constitute a legally binding contract between you and SIMA GmbH.

Please review these documents carefully prior to downloading.}}

==Client==

{{Colored_box|Text=Please make sure to '''EXACTLY match your RUTOS''' version when downloading your Bondix client.

Example: If your router is updated to 07.22.1, our Bondix version 1.26.01.2/07.22 is '''NOT the correct version''' and you need to '''DOWNGRADE''' your router to 07.22 to be able to use Bondix.}}

===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!1.25.7.6/07.20.3 (Prev)
!1.26.01.3/07.22.3 (Stable)
!1.26.01.3/07.23.5 (Latest)
|-

|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTX_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTX_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTX_R_00.07.23.5.tar.gz Download]
|-
|RUTM
|RUTM09, RUTM10, RUTM11, RUTM16, RUTM20, RUTM30, RUTM31, RUTM50, RUTM51, RUTM52, RUTM54, RUTM55, RUTM56, RUTM59
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTM_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTM_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTM_R_00.07.23.5.tar.gz Download]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956, RUT976, RUT981, RUT986
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT9M_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT9M_R_00.07.23.5.tar.gz Download]
|-
|RUT2M
|RUT200, RUT202, RUT204, RUT206, RUT241, RUT260, RUT271, RUT276, RUT281
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT2M_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUT2M_R_00.07.23.5.tar.gz Download]
|-
|RUTC
|RUTC40, RUTC41, RUTC42, RUTC50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTC_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTC_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTC_R_00.07.23.5.tar.gz Download]
|-
|RUTE
|RUT206, RUT271
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTE_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTE_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-RUTE_R_00.07.23.5.tar.gz Download]
|-
|OTD5
|OTD500
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-OTD5_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-OTD5_R_00.07.22.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.3-OTD5_R_00.07.23.5.tar.gz Download]
|-
|ATRM50
|ATRM50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-ATRM50_R_00.07.20.3.tar.gz Download]
|-
|ALTOS
|ALTOS
| Coming soon
|}

====EOL====
For routers designated as [https://teltonika-networks.com/support/eol-products "End of Production"] by Teltonika Networks, we no longer provide updated Bondix Client versions. If your device is marked as EOL and you require further support or newer versions, please contact us directly via email.

==Server==

===Latest Version (1.26.01.2)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.26.01.2.sh install-bondix-server-1.26.01.2.sh]

===Stable Version (1.25.7.6)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.25.7.6.sh install-bondix-server-1.25.7.6.sh]

Proceed to [[Manuals/Server| Installing a Bondix Server]].

Manuals/Server

2026-05-21T09:39:01Z

Sylvia: /* Installing the Linux VM (Ubuntu 20.4-24.04) */

== Preparations ==
To install the Bondix server, you will need a few minutes of stable Internet, a web browser, and possibly some coffee or tea.

=== Supported Browsers ===
The following browsers have been tested to function properly with the Bondix server:
* Google Chrome
* MS Edge
* Mozilla Firefox

=== Updating the Bondix Server ===
If you want to update your Bondix server version, first delete the old installation scripts on your Linux VM by using the following command:

<nowiki>rm install-bondix-server.sh*</nowiki>

After that, just repeat the installation process as described above.

⚠️ '''This will NOT delete your server configuration! It will only delete the installation scripts and a recommended measure before updating your server.''' ⚠️

=== Installing the Linux VM (Ubuntu 20.4-26.04 LTS) ===
⚠️ '''For the installation, you will need root rights.''' ⚠️

Set your firewalls to the following settings:
Bondix server port shares
- TCP: 443, 80
- UDP: 44343
SSH (Optional): 22

Make sure your server has a public static IP and is reachable from the Internet.

Execute the following script in the terminal window of your server to download the latest version of the Bondix server:
<nowiki>wget https://releases.bondix.dev/endpoint/install-bondix-server.sh</nowiki>

<gallery widths="500" heights="300">
File:1-linux-install.png
</gallery>

To start the installation, enter the following commands:
<nowiki>chmod a+x install-bondix-server.sh
sudo ./install-bondix-server.sh</nowiki>

Confirm all the following prompts with the Enter key for a standard installation.

<gallery widths="500" heights="300">
File:2-linux-install.png
</gallery>

After completing the installation, you can reach the Bondix server web interface at the IP address shown. Log in with the username “admin” and the password previously generated during installation.

<gallery widths="300" heights="200">
File:3-login.png
</gallery>

== Bondix Server ==
=== Licensing ===
If your server is not already licensed, you first need to activate the Bondix Server Tunnel license under the menu item “Licensing”.

<gallery widths="500" heights="300" perrow="2">
File:4-nolicense.png
File:5-activate-license.png
</gallery>

Enter the Bondix license key here, as well as a valid email address to which the license key is bound. You can also enter a name for the server instance here. Then press “Submit”.

<gallery widths="300" heights="200">
File:6-license-key.png
</gallery>

After the successful activation, the Licensing overview will display the number of licensed tunnels as well as the expiry date of your active tunnel subscriptions with the respective expiry date and the maximum number of active server instances possible under this license number.

<gallery widths="500" heights="300">
File:7-successful-activation.png
</gallery>

You can add further additional tunnels/server instances at any time under the item “Activate License”.

=== Administration ===
==== Overview ====
This is the web interface of a licensed Bondix server.

<gallery widths="500" heights="500">
File:8-overview.png
</gallery>

==== Bondix Tunnels ====
To connect a Bondix-compatible router to a Bondix server, you first need to create a tunnel for this respective router. Only then does the server know that there will be a new router to receive data from and send data to.

===== Create a new tunnel =====
Navigate to the menu item “Tunnel”. Select the tunnel environment for which you want to create the tunnel by clicking the corresponding tab; the default is set to “env0”. Then, assign a unique tunnel name and press “Create”.

⚠️ '''The tunnel name must not contain any spaces.''' ⚠️

<gallery widths="500" heights="300" perrow="2">
File:9-add-tunnel.png
File:10-add-tunnel-detail.png
</gallery>

You will then automatically be navigated to the settings window of the newly created tunnel. There, set a password for establishing the connection, make sure that “Enabled” is ticked, and then press “Save”.

<gallery widths="500" heights="300">
File:11-tunnel-added.png
</gallery>

Your tunnel is now displayed under the menu item “Overview”. You can access settings for each tunnel simply by clicking on the tunnel name.

<gallery widths="500" heights="300">
File:12-tunnel-overview.png
</gallery>

===== Connect a compatible router to a Bondix server. =====
Make sure that the latest Bondix client is installed on your router. Go to the settings menu of your router’s Bondix client and enter the server’s IP address and the tunnel name and password you created in chapter 3.2.2 in the corresponding fields. Save your entry and then restart the service (Restart Service).

<gallery widths="500" heights="500">
File:13-tunnel-credentials.png
</gallery>

The tunnel is now listed in the Bondix server’s menu “Overview” including the number of its active connections. Click on the tunnel name to access the tunnel settings and options.

<gallery widths="500" heights="300">
File:12-tunnel-overview.png
</gallery>

===== Tunnel details and settings =====
====== Functions ======

<gallery widths="500" heights="500">
File:14-functions.png
</gallery>

{| class="wikitable"
! Function !! Effect
|-
| 1 Enabled || Activates (ticked) or deactivates (unticked) the tunnel.
|-
| 2 Revert || Undoes any changes that have not yet been saved.
|-
| 3 Save || Saves changes.
|-
| 4 Channel || Provides an overview of channels currently connected.
|}

''' Function “Override Client Settings” '''
If you activate this on server side, local tunnel presets and WAN priority settings of the connected router are overwritten or reset by the server’s settings. You will need to restart the tunnel.

<gallery widths="500" heights="300">
File:15-override-client-settings.png
</gallery>

====== Actions ======

<gallery widths="500" heights="500">
File:16-actions.png
</gallery>

{| class="wikitable"
! Function !! Effect
|-
| 1 Restart tunnel || Allows the tunnel connection to be disconnected briefly and then reconnected. This is needed for some changes to take effect.
|-
| 2 Open Monitor || Displays a graphical overview of the connections of the router.
|-
| 3 Expert Settings || Opens the server-side Bondix web monitor for diagnostic purposes.
|-
| 4 Delete Tunnel || Deletes a tunnel permanently without the possibility to restore it.
|}

===== Tunnel Environments =====
In Bondix, a tunnel environment is a pool of resources used by a group of tunnels. This includes packet cache, CPU core, a UDP listener, and a virtual network interface.

====== Add Environments ======
During the Bondix server installation, the software automatically creates a default environment with the name “env0”. You can create and add further environments via the menu item “Add Environment”.

<gallery widths="500" heights="300">
File:17-tunnel-environments.png
</gallery>

====== UDP Listener settings ======
For common scenarios, select “0.0.0.0 (Any Interface)” for the UDP Listener IP.

⚠️ '''Each environment must be assigned its own unique UDP Listener Port. This port must not be used elsewhere in the system, and it must not be blocked by a firewall.''' ⚠️

====== Virtual Interface settings ======
Leave the Virtual Interface Name blank to automatically generate a name for it.

⚠️ '''The Virtual Interface Name and the Virtual Network (CIDR) assigned to the Tunnel Environment must also be unique, not to be used in any other environment.''' ⚠️

====== Outgoing settings ======
The Outgoing Interface describes where you want to route your data traffic. Optionally, you can enter a specific Outgoing IP address.

====== Activate Tunnel-to-Tunnel Communication ======
The option “Disable traffic among routers” is activated by default due to Bondix providing multi-tenancy support. This feature prevents routers assigned to a Tunnel Environment from communicating with each other. If you deactivate “Disable traffic among routers”, routers in the same environment can interact. You can adjust this setting separately for each environment.

== Troubleshooting ==
Sometimes, your Bondix server may not work as expected. If that happens, you may find possible solutions in this section.
{| class="wikitable"
! Problem !! Solution
|-
| ? || Re-install Server (Update)
|-
| ? || Remove Server
|-
| ? || Start Bondix Service
|-
| ? || Stop Bondix Service
|-
| ? || Server update notification in Web interface update via console
|}

== Bondix Server Log ==
This is an exemplary overview of a server’s current log messages:

<gallery widths="500" heights="300">
File:18-server-log.png
</gallery>

Main Page

2026-05-06T11:32:22Z

Sylvia: /* Bondix Essential Cloud */

Main Page

2026-05-06T11:32:07Z

Sylvia: /* Bondix Essential Cloud */

{{DISPLAYTITLE:Start}}

== Welcome! ==

This is the Bondix Wiki, our ever-growing knowledge base. Here, we collect all things Bondix. We offer handy quick-start information but also in-depth how-tos for installation, debugging, and general understanding, as well as pretty-looking and informative marketing material.

Feel free to roam around and take all the wisdom you need to bring your Bondix knowledge and understanding to the next level.

== Get Started ==

This section helps you get your Bondix system up and running in no time.

=== Bondix Essential Cloud ===

#[[Howto essential|Bondix Hosted Essential How-To]] Setup Bondix Hosted Essential on your Teltonika device.

=== Classic Bondix Installation ===
# <big>'''[[Downloads|Download the latest release versions]]'''</big> Download the latest Bondix software suitable for your device and see changelogs and release notes. Download & installation are free-of-charge for all of our software.
# [[Client Installation|Bondix Client Installation]] Install Bondix on your Teltonika device.
# [[Server|Bondix Server Installation]] Install and configure your Bondix server.

{{Colored_box|Text=Bondix Licenses have a fixed start and end date and cannot be renewed. If they expire, you need to purchase a new Bondix license code and insert it into your server the same way you did the first time: [[Server|Bondix Server Installation]]!}}

=== Bondix CloudLink Bundle ===

If you want to get your '''Bondix CloudLink Bundle''' up and running, our partner [https://www.unwirednetworks.com Unwired Networks] has a detailed step-by-step manual for that: [https://docs.unwirednetworks.com/docs/cloudlink/teltonika_cloudlink.html Bondix CloudLink]

{{Colored_box|Text=If you need technical assistance, please open up a support ticket in our [https://support.bondix.net/ Bondix Support Portal]!}}
=== Manuals ===
In our manuals, you can find more detailed information on different settings and values that can cater to special circumstances, environments, and needs. They are updated continually, so screenshots may vary. The overall system is the same.
* [[Manuals/Client|Bondix on Teltonika devices]]
** [[Client Installation]]
** [[General Teltonika Router Settings]]
** [[Configuration Mode]]
** [[Tunnel Preset]]
** [[Interfaces]]
** [[Advanced Settings]]
** [[Layer 2]]
** [[Monitor 7.02.x]]
** [[Status]]
* [[Manuals/Server|Bondix Server Setup]]
** [https://docs.unwirednetworks.com/docs/cloudlink/teltonika_cloudlink.html Bondix CloudLink]
** [[my.bondix.cloud]]
* [[Manuals/Webshop|How to order Bondix in the Bondix Webshop]]

== General Information ==
This section gives you information on what Bondix is and how it works. Also, it's where we collect FAQs and especially their answers.
* [[Architecture]]
* [[Licenses]]
* [[FAQs]]

== Deep-dive Topics ==
In this section, you'll find specialized knowledge that is very technical and/or serves as a how-to for special use cases.
=== Client and Server ===
* [[Transparent Bonding Proxy]]
* [[Teltonika Portforwarding|General port forwarding]]
* [[Quality of Service]]
* [[Layer2]]
* [[Presets]]
* [[QuickConnect]]
* [[DMZ and 1:1 NAT configuration]]

=== Client ===
* [[Client/StaticRoutes|How to create static routes]]
* [[Teltonika Portforwarding|How to create a port-forward with Teltonika Routers]]
* [[Starlink|Bondix and Starlink]]
* [[Client]]
* [[Client/OpenWRT]]
* [[Client/RUTX12]]
* [[Client Configuration]]

=== Server ===
* [[Certificates|How to setup certificate-based authorization]]
* [[Server Capacity|How to calculate how many Bondix Servers you need]]
* [[Server Licensing|How to add licenses to your Bondix Server]]
* [[Server/Access Control]]
* [[Server/Changing Ports]]
* [[Server/Configuration]]
* [[Server/Routes]]
* [[Server Certificates with LetsEncrypt]]
* [[Server Configuration]]

== Marketing Material ==
Here, you can find all marketing material we have to share in one place.

===== Basic Product Info =====
[[File:Bondix-product-info-2024.pdf|thumb]]
[[File:Bondix-product-info-2024-de.pdf|thumb]]

Product images
<gallery>
Bondix-product-license-trial-web.png|Product image Trial license
Bondix-product-license-iot-web.png|Product image IoT license
Bondix-product-license-standard-web.png|Product image Standard license
Bondix-product-license-enterprise-web.png|Product image Enterprise license
Bondix-product-license-ultimate-web.png|Product image Ultimate license
</gallery>

===== Presentations =====
'''Generic'''

[[File:Presentation-bondix-wan-bonding-generic-202308.pdf|thumb|What is WAN Bonding?]] 
[[File:Presentation-bondix-licensing-202309.pdf|thumb|Bondix licensing in a tiny nutshell]]

'''Teltonika-specific'''

[[File:Bondix-webinar-dec2022-web2.pdf|thumb|Joint webinar Bondix and Teltonika, Dec 2022]] -->
[https://youtu.be/GSKhc_qOp1o YouTube - Paving New Bonding Possibilities in IIoT]

Downloads

2026-05-04T12:25:23Z

Sylvia: /* Packages */

= Bondix Software Downloads =

This page provides download links for Bondix software compatible with various devices and firmware versions. Select the appropriate file based on your device model and firmware version.

'''Current Release Version:''' 1.26.01.x''' '''
{{Colored_box|Text=By initiating the download of the software from this site, you hereby acknowledge and consent to be bound by the terms of our [https://www.bondixintelligence.com/_files/ugd/226d8a_e5e6dbbc57124ed985bad80fa49ccbc8.pdf End User License Agreement (EULA)] and Terms of Use, which constitute a legally binding contract between you and SIMA GmbH.

Please review these documents carefully prior to downloading.}}

==Client==

{{Colored_box|Text=Please make sure to '''EXACTLY match your RUTOS''' version when downloading your Bondix client.

Example: If your router is updated to 07.22.1, our Bondix version 1.26.01.2/07.22 is '''NOT the correct version''' and you need to '''DOWNGRADE''' your router to 07.22 to be able to use Bondix.}}

===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!1.25.7.6/07.20.3 (Prev)
!1.26.01.2/07.21.3 (Stable)
!1.26.01.2/07.22 (Latest)
|-

|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTX_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTX_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTX_R_00.07.22.tar.gz Download]
|-
|RUTM
|RUTM09, RUTM10, RUTM11, RUTM16, RUTM20, RUTM30, RUTM31, RUTM50, RUTM51, RUTM52, RUTM54, RUTM55, RUTM56, RUTM59
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTM_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTM_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTM_R_00.07.22.tar.gz Download]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956, RUT976, RUT981, RUT986
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT9M_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT9M_R_00.07.22.tar.gz Download]
|-
|RUT2M
|RUT200, RUT202, RUT204, RUT206, RUT241, RUT260, RUT271, RUT276, RUT281
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT2M_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT2M_R_00.07.22.tar.gz Download]
|-
|RUTC
|RUTC40, RUTC41, RUTC42, RUTC50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTC_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTC_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTC_R_00.07.22.tar.gz Download]
|-
|RUTE
|RUT206, RUT271
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTE_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTE_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTE_R_00.07.22.tar.gz Download]
|-
|OTD5
|OTD500
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-OTD5_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-OTD5_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-OTD5_R_00.07.22.tar.gz Download]
|-
|ATRM50
|ATRM50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-ATRM50_R_00.07.20.3.tar.gz Download]
|-
|ALTOS
|ALTOS
| Coming soon
|}

====EOL====
For routers designated as [https://teltonika-networks.com/support/eol-products "End of Production"] by Teltonika Networks, we no longer provide updated Bondix Client versions. If your device is marked as EOL and you require further support or newer versions, please contact us directly via email.

==Server==

===Latest Version (1.26.01.2)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.26.01.2.sh install-bondix-server-1.26.01.2.sh]

===Stable Version (1.25.7.6)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.25.7.6.sh install-bondix-server-1.25.7.6.sh]

Proceed to [[Manuals/Server| Installing a Bondix Server]].

Downloads

2026-05-04T12:25:01Z

Sylvia: /* Packages */

= Bondix Software Downloads =

This page provides download links for Bondix software compatible with various devices and firmware versions. Select the appropriate file based on your device model and firmware version.

'''Current Release Version:''' 1.26.01.x''' '''
{{Colored_box|Text=By initiating the download of the software from this site, you hereby acknowledge and consent to be bound by the terms of our [https://www.bondixintelligence.com/_files/ugd/226d8a_e5e6dbbc57124ed985bad80fa49ccbc8.pdf End User License Agreement (EULA)] and Terms of Use, which constitute a legally binding contract between you and SIMA GmbH.

Please review these documents carefully prior to downloading.}}

==Client==

{{Colored_box|Text=Please make sure to '''EXACTLY match your RUTOS''' version when downloading your Bondix client.

Example: If your router is updated to 07.22.1, our Bondix version 1.26.01.2/07.22 is '''NOT the correct version''' and you need to '''DOWNGRADE''' your router to 07.22 to be able to use Bondix.}}

===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!1.25.7.6/07.20.3 (Prev)
!1.26.01.2/07.21.3 (Stable)
!1.26.01.2/07.22 (Latest)
|-

|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTX_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTX_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTX_R_00.07.22.tar.gz Download]
|-
|RUTM
|RUTM09, RUTM10, RUTM11, RUTM16, RUTM20, RUTM30, RUTM31, RUTM50, RUTM51, RUTM52, RUTM54, RUTM55, RUTM56, RUTM59
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTM_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTM_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTM_R_00.07.22.tar.gz Download]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956, RUT976, RUT981, RUT986
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT9M_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT9M_R_00.07.22.tar.gz Download]
|-
|RUT2M
|RUT200, RUT202, RUT204, RUT206, RUT241, RUT260, RUT271, RUT276, RUT281
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT2M_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT2M_R_00.07.22.tar.gz Download]
|-
|RUTC
|RUTC40, RUTC41, RUTC42, RUTC50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTC_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTC_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTC_R_00.07.22.tar.gz Download]
|-
|RUTE
|RUT206, RUT271
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTE_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTE_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTE_R_00.07.22.tar.gz Download]
|-
|OTD5
|OTD500
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-OTD5_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-OTD5_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-OTD5_R_00.07.22.tar.gz Download]
|-
|ATRM50
|ATRM50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-ATRM50_R_00.07.20.3.tar.gz Download]
|-
|ALTOS
|ALTOS
| Coming soon
|
|}

====EOL====
For routers designated as [https://teltonika-networks.com/support/eol-products "End of Production"] by Teltonika Networks, we no longer provide updated Bondix Client versions. If your device is marked as EOL and you require further support or newer versions, please contact us directly via email.

==Server==

===Latest Version (1.26.01.2)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.26.01.2.sh install-bondix-server-1.26.01.2.sh]

===Stable Version (1.25.7.6)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.25.7.6.sh install-bondix-server-1.25.7.6.sh]

Proceed to [[Manuals/Server| Installing a Bondix Server]].

Downloads

2026-05-04T12:24:43Z

Sylvia: /* Packages */

= Bondix Software Downloads =

This page provides download links for Bondix software compatible with various devices and firmware versions. Select the appropriate file based on your device model and firmware version.

'''Current Release Version:''' 1.26.01.x''' '''
{{Colored_box|Text=By initiating the download of the software from this site, you hereby acknowledge and consent to be bound by the terms of our [https://www.bondixintelligence.com/_files/ugd/226d8a_e5e6dbbc57124ed985bad80fa49ccbc8.pdf End User License Agreement (EULA)] and Terms of Use, which constitute a legally binding contract between you and SIMA GmbH.

Please review these documents carefully prior to downloading.}}

==Client==

{{Colored_box|Text=Please make sure to '''EXACTLY match your RUTOS''' version when downloading your Bondix client.

Example: If your router is updated to 07.22.1, our Bondix version 1.26.01.2/07.22 is '''NOT the correct version''' and you need to '''DOWNGRADE''' your router to 07.22 to be able to use Bondix.}}

===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!1.25.7.6/07.20.3 (Prev)
!1.26.01.2/07.21.3 (Stable)
!1.26.01.2/07.22 (Latest)
|-

|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTX_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTX_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTX_R_00.07.22.tar.gz Download]
|-
|RUTM
|RUTM09, RUTM10, RUTM11, RUTM16, RUTM20, RUTM30, RUTM31, RUTM50, RUTM51, RUTM52, RUTM54, RUTM55, RUTM56, RUTM59
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTM_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTM_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTM_R_00.07.22.tar.gz Download]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956, RUT976, RUT981, RUT986
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT9M_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT9M_R_00.07.22.tar.gz Download]
|-
|RUT2M
|RUT200, RUT202, RUT204, RUT206, RUT241, RUT260, RUT271, RUT276, RUT281
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT2M_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT2M_R_00.07.22.tar.gz Download]
|-
|RUTC
|RUTC40, RUTC41, RUTC42, RUTC50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTC_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTC_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTC_R_00.07.22.tar.gz Download]
|-
|RUTE
|RUT206, RUT271
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTE_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTE_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTE_R_00.07.22.tar.gz Download]
|-
|OTD5
|OTD500
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-OTD5_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-OTD5_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-OTD5_R_00.07.22.tar.gz Download]
|-
|ATRM50
|ATRM50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-ATRM50_R_00.07.20.3.tar.gz Download]
|-
|ALTOS
|ALTOS
| Coming soon
|
|
|}

====EOL====
For routers designated as [https://teltonika-networks.com/support/eol-products "End of Production"] by Teltonika Networks, we no longer provide updated Bondix Client versions. If your device is marked as EOL and you require further support or newer versions, please contact us directly via email.

==Server==

===Latest Version (1.26.01.2)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.26.01.2.sh install-bondix-server-1.26.01.2.sh]

===Stable Version (1.25.7.6)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.25.7.6.sh install-bondix-server-1.25.7.6.sh]

Proceed to [[Manuals/Server| Installing a Bondix Server]].

Downloads

2026-04-27T08:55:03Z

Sylvia: /* Client */

= Bondix Software Downloads =

This page provides download links for Bondix software compatible with various devices and firmware versions. Select the appropriate file based on your device model and firmware version.

'''Current Release Version:''' 1.26.01.x''' '''
{{Colored_box|Text=By initiating the download of the software from this site, you hereby acknowledge and consent to be bound by the terms of our [https://www.bondixintelligence.com/_files/ugd/226d8a_e5e6dbbc57124ed985bad80fa49ccbc8.pdf End User License Agreement (EULA)] and Terms of Use, which constitute a legally binding contract between you and SIMA GmbH.

Please review these documents carefully prior to downloading.}}

==Client==

{{Colored_box|Text=Please make sure to '''EXACTLY match your RUTOS''' version when downloading your Bondix client.

Example: If your router is updated to 07.22.1, our Bondix version 1.26.01.2/07.22 is '''NOT the correct version''' and you need to '''DOWNGRADE''' your router to 07.22 to be able to use Bondix.}}

===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!1.25.7.6/07.20.3 (Prev)
!1.26.01.2/07.21.3 (Stable)
!1.26.01.2/07.22 (Latest)
|-

|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTX_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTX_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTX_R_00.07.22.tar.gz Download]
|-
|RUTM
|RUTM08, RUTM09, RUTM10, RUTM11, RUTM30, RUTM50, RUTM51, RUTM52, RUTM54, RUTM59
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTM_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTM_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTM_R_00.07.22.tar.gz Download]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT9M_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT9M_R_00.07.22.tar.gz Download]
|-
|RUT2M
|RUT200, RUT241, RUT260
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT2M_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUT2M_R_00.07.22.tar.gz Download]
|-
|RUTC
|RUTC50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTC_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTC_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTC_R_00.07.22.tar.gz Download]
|-
|RUTE
|RUT206, RUT271
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-RUTE_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTE_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-RUTE_R_00.07.22.tar.gz Download]
|-
|OTD5
|OTD500
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-OTD5_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-OTD5_R_00.07.21.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.2-OTD5_R_00.07.22.tar.gz Download]
|-
|ATRM50
|ATRM50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-ATRM50_R_00.07.20.3.tar.gz Download]
|
|
|}

====EOL====
For routers designated as [https://teltonika-networks.com/support/eol-products "End of Production"] by Teltonika Networks, we no longer provide updated Bondix Client versions. If your device is marked as EOL and you require further support or newer versions, please contact us directly via email.

==Server==

===Latest Version (1.26.01.2)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.26.01.2.sh install-bondix-server-1.26.01.2.sh]

===Stable Version (1.25.7.6)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.25.7.6.sh install-bondix-server-1.25.7.6.sh]

Proceed to [[Manuals/Server| Installing a Bondix Server]].