Bondix Wiki - User contributions [en]

Downloads

2026-03-16T11:30:52Z

Red:

= 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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!1.25.7.6/07.20.3 (Stable)
!1.26.01.1/07.20.3 (Latest)
!1.26.01.1/07.21.1 (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.1-RUTX_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUTX_R_00.07.21.1.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.1-RUTM_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUTM_R_00.07.21.1.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.1-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUT9M_R_00.07.21.1.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.1-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUT2M_R_00.07.21.1.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.1-RUTC_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUTC_R_00.07.21.1.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.1-RUTE_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUTE_R_00.07.21.1.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.1-OTD5_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-OTD5_R_00.07.21.1.tar.gz Download]
|-
|ATRM50
|ATRM50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-ATRM50_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-ATRM50_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-ATRM50_R_00.07.21.1.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]].

Downloads

2026-03-13T15:50:17Z

Red:

= 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.1''' '''
{{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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!1.25.7.6/07.20.3 (Stable)
!1.26.01.1/07.20.3 (Latest)
!1.26.01.1/07.21.1 (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.1-RUTX_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUTX_R_00.07.21.1.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.1-RUTM_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUTM_R_00.07.21.1.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.1-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUT9M_R_00.07.21.1.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.1-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUT2M_R_00.07.21.1.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.1-RUTC_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUTC_R_00.07.21.1.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.1-RUTE_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-RUTE_R_00.07.21.1.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.1-OTD5_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-OTD5_R_00.07.21.1.tar.gz Download]
|-
|ATRM50
|ATRM50
|[https://cdn.bondix.dev/files/bondixclient-1.25.7.6-ATRM50_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-ATRM50_R_00.07.20.3.tar.gz Download]
|[https://cdn.bondix.dev/files/bondixclient-1.26.01.1-ATRM50_R_00.07.21.1.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.1)===
*[https://cdn.bondix.dev/endpoint/install-bondix-server-1.26.01.1.sh install-bondix-server-1.26.01.1.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-02-28T14:19:50Z

Red:

= 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.1''' '''
{{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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!1.25.7.6/07.20.3 (Stable)
!1.26.01.1/07.20.3 (Latest)
!1.26.01.1/07.21.1 (Latest)
|-
|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://releases.bondix.dev/files/bondixclient-1.25.7.6-RUTX_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUTX_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUTX_R_00.07.21.1.tar.gz Download]
|-
|RUTM
|RUTM08, RUTM09, RUTM10, RUTM11, RUTM30, RUTM50, RUTM51, RUTM52, RUTM54, RUTM59
|[https://releases.bondix.dev/files/bondixclient-1.25.7.6-RUTM_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUTM_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUTM_R_00.07.21.1.tar.gz Download]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956
|[https://releases.bondix.dev/files/bondixclient-1.25.7.6-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUT9M_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUT9M_R_00.07.21.1.tar.gz Download]
|-
|RUT2M
|RUT200, RUT241, RUT260
|[https://releases.bondix.dev/files/bondixclient-1.25.7.6-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUT2M_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUT2M_R_00.07.21.1.tar.gz Download]
|-
|RUTC
|RUTC50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.6-RUTC_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUTC_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUTC_R_00.07.21.1.tar.gz Download]
|-
|RUTE
|RUT206, RUT271
|[https://releases.bondix.dev/files/bondixclient-1.25.7.6-RUTE_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUTE_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-RUTE_R_00.07.21.1.tar.gz Download]
|-
|OTD5
|OTD500
|[https://releases.bondix.dev/files/bondixclient-1.25.7.6-OTD5_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-OTD5_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-OTD5_R_00.07.21.1.tar.gz Download]
|-
|ATRM50
|ATRM50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.6-ATRM50_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-ATRM50_R_00.07.20.3.tar.gz Download]
|[https://releases.bondix.dev/files/bondixclient-1.26.01.1-ATRM50_R_00.07.21.1.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.1)===
*[https://releases.bondix.dev/endpoint/install-bondix-server-1.26.01.1.sh install-bondix-server-1.26.01.1.sh]

===Stable Version (1.25.7.6)===
*[https://releases.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]].

Server/User Management

2026-01-22T13:56:17Z

Red:

(this is a work in progress article for the upcoming 1.26.01 Bondix release. Content is subject to change.)
=Overview=
The Managed User system provides a complete user management solution for the BondingServer, including tunnel management, port forwarding, QoS settings, and optional remote synchronization. This system is designed for multi-tenant scenarios where users need to manage their own tunnels through a dedicated web interface.
=Modes of Operation=

The system operates in two modes:
==Local Mode (Default)==

*Configuration stored in a local JSON file
*No remote synchronization
*Ideal for single-server deployments
*All configuration changes saved locally
==Remote Mode==

*Configuration synchronized with a remote server
*Periodic sync every 30 minutes
*Changes pushed to remote server automatically
*Events sent to webhook endpoint
*Ideal for distributed/multi-server deployments
=Local Configuration File Layout=

While users can be stored in the main server configuration, it’s '''discouraged'''. Using a separate configuration file offers greater flexibility and cleaner separation.

'''Recommended file''': <code>/path/to/managed-users.json</code>

'''Structure''':
{
"version": 1,
"config": {
"user@example.com": {
"password": "sha256_hash",
"tunnels": [
{
"config": {
"name": "office-tunnel",
"enabled": true,
"password": "tunnel_password",
"mtu": 1500,
"qos": "default"
}
}
],
"portForwarding": [],
"qos": []
},
"admin@example.com": {
"password": "sha256_hash",
"tunnels": [
{
"config": {
"name": "main-tunnel",
"enabled": true,
"password": "secure_pass",
"mtu": 1400,
"qos": "custom"
}
}
],
"portForwarding": [],
"qos": {
"classes": [
{
"name": "high-priority",
"priority": 1,
"bandwidth": 1000,
"rules": []
}
]
}
}
}
}
'''Root Fields''':

* <code>version</code>: Configuration version number (uint64, required)
* <code>config</code>: Object containing user configurations keyed by username

'''Per-User Fields''':

* <code>password</code>: SHA256 hash of the user’s password
* <code>tunnels</code>: Array of tunnel configurations
* <code>portForwarding</code>: Array of port forwarding rules ('''currently not implemented!''')
* <code>qos</code>: QoS configuration object
* Enabling Managed Users

'''Action''': <code>enable-user-management</code>

The following command must be added to <code>/etc/bondixserver.json</code>

'''Configuration JSON''':
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/path/to/managed-users.json"
},
"caFile": "/etc/ssl/certs/root-ca.pem"
}

{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json"
}
}
'''Settings Object Fields''':

* <code>config</code>: Path to local configuration file (string, required for local mode)
* <code>configEndpoint</code>: Remote sync URL (string, optional)
* <code>configAuth</code>: Authentication token for remote endpoints (string, optional)
* <code>eventEndpoint</code>: Webhook URL for events (string, optional)
* <code>users</code>: Array of initial users (optional, discouraged)

'''SSL/TLS Options''':

* <code>caDirectory</code>: Directory containing CA certificates
* <code>caFile</code>: Single CA file path
=Remote Mode Configuration=

When <code>configEndpoint</code> is specified, the system operates in remote mode:
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json",
"configEndpoint": "https://management.example.com/api/config",
"configAuth": "Bearer universal_auth_token",
"eventEndpoint": "https://management.example.com/api/events"
}
}
'''Remote Sync Behavior''':

# '''Initial Fetch''': On startup, fetches configuration from remote endpoint
# '''Periodic Sync''': Every 30 minutes, checks for remote updates
# '''Change Push''': Every 5 seconds after local changes, syncs to remote
# '''Version Control''': Uses version numbers to prevent conflicts

'''Event Webhook Events''':

<code>password_request</code>: Triggered when user requests password reset - Payload includes temporary password for the user

'''Remote Endpoint Requirements''':

* <code>configEndpoint</code> must accept GET for fetch and POST for store
* Both endpoints require <code>Authorization</code> header with configured auth token
* Fetch returns 204 if no newer version exists, 200 with config JSON otherwise

=Web Frontend=

'''Frontend Location''': <code>/user</code>

'''Automatic Redirect''': When user management is enabled, the server automatically redirects requests from <code>/</code> to <code>/user</code>. Use /admin for full access.

The frontend provides:

* User login interface
* Tunnel management dashboard
* QoS settings management
* Password change functionality

TODO: Port forwarding configuration to be implemented.

=API Endpoints=

All endpoints require authentication via Bearer token or universal auth token.
==Authentication Endpoints==

'''POST <code>/api/login</code>'''
// Request
{
"username": "user@example.com",
"password": "password"
}

// Response (200 OK)
{
"token": "session_token",
"user": {
"email": "user@example.com",
"name": "User"
}
}

 // Response (401 Unauthorized)
{"allowReset": true} // If eventEndpoint configured

'''POST <code>/api/forgot-password</code>'''
// Request
{
"email": "user@example.com"
}

 // Response: 204 No Content (if user exists and eventEndpoint configured)

==Configuration Endpoints==

'''GET <code>/api/config</code>'''
// Response
{
"tunnels": [...],
"portForwarding": [...],
"qos": [...]
}

'''POST <code>/api/config</code>'''
// Request
{
"tunnels": [
{
"config": {
"name": "tunnel_name",
"enabled": true,
"password": "new_password",
"mtu": 1500,
"qos": "default"
}
}
],
"portForwarding": [...],
"qos": [...]
}

// Response
{
"tunnels": [...],
"portForwarding": [...],
"qos": [...]
}
'''Important''': This endpoint is the primary method for updating any configuration. When remote mode is enabled, calling this endpoint triggers the synchronization methods automatically.

'''POST <code>/api/change-password</code>'''
// Request
{
"currentPassword": "old_password",
"newPassword": "new_password"
}

// Response
{"result": "ok"}

==Tunnel Management Endpoints==

'''GET <code>/api/status</code>'''
// Response
{
"tunnel": [
{
"name": "tunnel_name",
"status": "connected|disconnected|disabled",
"uptime": 12345,
"clientIp": "10.0.0.1/24",
"gatewayIp": "10.0.0.254",
"channelConnected": 2,
"currentIncoming": 1024,
"currentOutgoing": 2048,
"activeProxyConnections": 1,
"qosName": "default",
"totalIncoming": 1024000,
"totalOutgoing": 2048000,
"environment": "env_name",
"connectedChannels": 2,
"channels": [
{
"status": "connected",
"enabled": true,
"name": "channel_name",
"interface": "eth0",
"address": "10.0.0.1",
"uptime": 3600,
"lastError": "",
"totalOutgoing": 512000,
"totalIncoming": 1024000,
"connectionAttempts": 1,
"connectionType": "TCP",
"stats": {
"currentLatency": 15,
"idleLatency": 10,
"inTransit": 1024,
"packetloss": 0.1
}
}
]
}
]
}

'''POST <code>/api/restart</code>'''
// Request
{
"tunnel": "tunnel_name"
}

// Response
{"result": "ok"}

=Universal Authentication Token=

For third-party frontend integration or administrative operations, a universal auth token can be used to impersonate any user.

'''Authentication Method''':

# Set Authorization header to the configured <code>configAuth</code> token
# Set <code>X-Username</code> header to the target user’s email

'''Example Request''':

TODO: add request

'''....'''

'''Security Note''': The universal auth token should be kept secure and only used for trusted applications.
==Tunnel Configuration Structure==
{
"config": {
"name": "tunnel_name",
"enabled": true,
"password": "tunnel_password",
"mtu": 1500,
"qos": "default|custom|<preset_name>"
}
}
'''Fields''':

* <code>name</code>: Unique tunnel identifier (string, required)
* <code>enabled</code>: Enable/disable tunnel (boolean, default: true)
* <code>password</code>: Tunnel password (string, required)
* <code>mtu</code>: MTU value between 1100-1500 (uint16, default: 1500)
* <code>qos</code>: QoS mode selection (string, default: “default”) - <code>"default"</code>: Use client QoS settings - <code>"custom"</code>: Use custom QoS configuration
* Other values: Use named QoS preset

=Port Forwarding Configuration=
TODO: currently not implemented
{
"enabled": true,
"tunnel": "tunnel_name",
"publicPort": 8080,
"targetIp": "192.168.1.100",
"targetPort": 80,
"description": "Web server forward"
}
'''Fields''':

* <code>enabled</code>: Enable/disable this port forward (boolean)
* <code>tunnel</code>: Associated tunnel name (string)
* <code>publicPort</code>: External port number (uint16)
* <code>targetIp</code>: Internal target IP address (string)
* <code>targetPort</code>: Internal target port (uint16)
* <code>description</code>: Note/description (string, max 1024 chars)
=QoS Configuration=
TODO
=Complete Example=

'''Enable Managed Users (Local Mode)''':
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json"
}
}
'''Remote Mode with Events''':
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json",
"configEndpoint": "https://management.example.com/api/config",
"configAuth": "Bearer abc123universal456",
"eventEndpoint": "https://management.example.com/api/events"
},
"caFile": "/etc/ssl/certs/root-ca.pem"
}
'''Initial Config File''' (<code>/etc/bondix/managed-users.json</code>):
{
"version": 1,
"config": {
"admin@example.com": {
"password": "5e884898da1904719...",
"tunnels": [
{
"config": {
"name": "office-tunnel",
"enabled": true,
"password": "secure123",
"mtu": 1500,
"qos": "default"
}
}
],
"portForwarding": [],
"qos": []
}
}
}
=Error Handling=

'''Common Error Responses''':

* <code>{"result": "error", "error": "already enabled"}</code> - Managed users already active
* <code>401 Unauthorized</code> - Invalid or missing authentication
* <code>403 Forbidden</code> - Invalid current password for change
* <code>500 Internal Server Error</code> - Server-side errors

'''Version Conflicts''':

When remote mode is enabled and version conflicts occur:

* Local changes with higher version take precedence
* Remote changes with higher version are applied
* Synchronization retries automatically

=Password Management Details=

'''Password Storage''':

Passwords stored as SHA256 hashes (OpenSSL 1.x/3.x compatible), no plaintext password storage.

'''Password Reset Flow''':

# User POSTs to <code>/api/forgot-password</code> with email
# Server generates 16-character temporary password
# Event sent to <code>eventEndpoint</code> with <code>eventType: "password_request"</code>
# Temporary password valid for 30 minutes
# Rate-limited to 15 minutes between requests

'''Password Change''':

* Requires current password verification
* New password hashed and stored
* Temporary password cleared on successful change

=Synchronization Timing=

'''Local Mode''':

* Changes saved immediately to config file
* No periodic sync required

'''Remote Mode''':

* Initial fetch on handler startup
* Store sync: Every 5 seconds after changes
* Fetch sync: Every 30 minutes if no pending changes
* Automatic retry on failure__NOINDEX__

Server/User Management

2026-01-22T13:51:53Z

Red: /* Enabling Managed Users */

(this is a work in progress article for the upcoming 1.26.01 Bondix release. Content is subject to change.)
==Overview==
The Managed User system provides a complete user management solution for the BondingServer, including tunnel management, port forwarding, QoS settings, and optional remote synchronization. This system is designed for multi-tenant scenarios where users need to manage their own tunnels through a dedicated web interface.
===Modes of Operation===

The system operates in two modes:
====Local Mode (Default)====

*Configuration stored in a local JSON file
*No remote synchronization
*Ideal for single-server deployments
*All configuration changes saved locally
====Remote Mode====

*Configuration synchronized with a remote server
*Periodic sync every 30 minutes
*Changes pushed to remote server automatically
*Events sent to webhook endpoint
*Ideal for distributed/multi-server deployments
===Local Configuration File Layout===

While users can be stored in the main server configuration, it’s '''discouraged'''. Using a separate configuration file offers greater flexibility and cleaner separation.

'''Recommended file''': <code>/path/to/managed-users.json</code>

'''Structure''':
{
"version": 1,
"config": {
"user@example.com": {
"password": "sha256_hash",
"tunnels": [
{
"config": {
"name": "office-tunnel",
"enabled": true,
"password": "tunnel_password",
"mtu": 1500,
"qos": "default"
}
}
],
"portForwarding": [],
"qos": []
},
"admin@example.com": {
"password": "sha256_hash",
"tunnels": [
{
"config": {
"name": "main-tunnel",
"enabled": true,
"password": "secure_pass",
"mtu": 1400,
"qos": "custom"
}
}
],
"portForwarding": [],
"qos": {
"classes": [
{
"name": "high-priority",
"priority": 1,
"bandwidth": 1000,
"rules": []
}
]
}
}
}
}
'''Root Fields''':

* <code>version</code>: Configuration version number (uint64, required)
* <code>config</code>: Object containing user configurations keyed by username

'''Per-User Fields''':

* <code>password</code>: SHA256 hash of the user’s password
* <code>tunnels</code>: Array of tunnel configurations
* <code>portForwarding</code>: Array of port forwarding rules ('''currently not implemented!''')
* <code>qos</code>: QoS configuration object
* Enabling Managed Users

'''Action''': <code>enable-user-management</code>

The following command must be added to <code>/etc/bondixserver.json</code>

'''Configuration JSON''':
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/path/to/managed-users.json"
},
"caFile": "/etc/ssl/certs/root-ca.pem"
}

{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json"
}
}
'''Settings Object Fields''':

* <code>config</code>: Path to local configuration file (string, required for local mode)
* <code>configEndpoint</code>: Remote sync URL (string, optional)
* <code>configAuth</code>: Authentication token for remote endpoints (string, optional)
* <code>eventEndpoint</code>: Webhook URL for events (string, optional)
* <code>users</code>: Array of initial users (optional, discouraged)

'''SSL/TLS Options''':

* <code>caDirectory</code>: Directory containing CA certificates
* <code>caFile</code>: Single CA file path
===Remote Mode Configuration===

When <code>configEndpoint</code> is specified, the system operates in remote mode:
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json",
"configEndpoint": "https://management.example.com/api/config",
"configAuth": "Bearer universal_auth_token",
"eventEndpoint": "https://management.example.com/api/events"
}
}
'''Remote Sync Behavior''':

# '''Initial Fetch''': On startup, fetches configuration from remote endpoint
# '''Periodic Sync''': Every 30 minutes, checks for remote updates
# '''Change Push''': Every 5 seconds after local changes, syncs to remote
# '''Version Control''': Uses version numbers to prevent conflicts

'''Event Webhook Events''':

<code>password_request</code>: Triggered when user requests password reset - Payload includes temporary password for the user

'''Remote Endpoint Requirements''':

* <code>configEndpoint</code> must accept GET for fetch and POST for store
* Both endpoints require <code>Authorization</code> header with configured auth token
* Fetch returns 204 if no newer version exists, 200 with config JSON otherwise

===Web Frontend===

'''Frontend Location''': <code>/user</code>

'''Automatic Redirect''': When user management is enabled, the server automatically redirects requests from <code>/</code> to <code>/user</code>. Use /admin for full access.

The frontend provides:

* User login interface
* Tunnel management dashboard
* QoS settings management
* Password change functionality

TODO: Port forwarding configuration to be implemented.

===API Endpoints===

All endpoints require authentication via Bearer token or universal auth token.
====Authentication Endpoints====

'''POST <code>/api/login</code>'''
// Request
{
"username": "user@example.com",
"password": "password"
}

// Response (200 OK)
{
"token": "session_token",
"user": {
"email": "user@example.com",
"name": "User"
}
}

 // Response (401 Unauthorized)
{"allowReset": true} // If eventEndpoint configured

'''POST <code>/api/forgot-password</code>'''
// Request
{
"email": "user@example.com"
}

 // Response: 204 No Content (if user exists and eventEndpoint configured)

====Configuration Endpoints====

'''GET <code>/api/config</code>'''
// Response
{
"tunnels": [...],
"portForwarding": [...],
"qos": [...]
}

'''POST <code>/api/config</code>'''
// Request
{
"tunnels": [
{
"config": {
"name": "tunnel_name",
"enabled": true,
"password": "new_password",
"mtu": 1500,
"qos": "default"
}
}
],
"portForwarding": [...],
"qos": [...]
}

// Response
{
"tunnels": [...],
"portForwarding": [...],
"qos": [...]
}
'''Important''': This endpoint is the primary method for updating any configuration. When remote mode is enabled, calling this endpoint triggers the synchronization methods automatically.

'''POST <code>/api/change-password</code>'''
// Request
{
"currentPassword": "old_password",
"newPassword": "new_password"
}

// Response
{"result": "ok"}

====Tunnel Management Endpoints====

'''GET <code>/api/status</code>'''
// Response
{
"tunnel": [
{
"name": "tunnel_name",
"status": "connected|disconnected|disabled",
"uptime": 12345,
"clientIp": "10.0.0.1/24",
"gatewayIp": "10.0.0.254",
"channelConnected": 2,
"currentIncoming": 1024,
"currentOutgoing": 2048,
"activeProxyConnections": 1,
"qosName": "default",
"totalIncoming": 1024000,
"totalOutgoing": 2048000,
"environment": "env_name",
"connectedChannels": 2,
"channels": [
{
"status": "connected",
"enabled": true,
"name": "channel_name",
"interface": "eth0",
"address": "10.0.0.1",
"uptime": 3600,
"lastError": "",
"totalOutgoing": 512000,
"totalIncoming": 1024000,
"connectionAttempts": 1,
"connectionType": "TCP",
"stats": {
"currentLatency": 15,
"idleLatency": 10,
"inTransit": 1024,
"packetloss": 0.1
}
}
]
}
]
}

'''POST <code>/api/restart</code>'''
// Request
{
"tunnel": "tunnel_name"
}

// Response
{"result": "ok"}

===Universal Authentication Token===

For third-party frontend integration or administrative operations, a universal auth token can be used to impersonate any user.

'''Authentication Method''':

# Set Authorization header to the configured <code>configAuth</code> token
# Set <code>X-Username</code> header to the target user’s email

'''Example Request''':

TODO: add request

'''....'''

'''Security Note''': The universal auth token should be kept secure and only used for trusted applications.
===Tunnel Configuration Structure===
{
"config": {
"name": "tunnel_name",
"enabled": true,
"password": "tunnel_password",
"mtu": 1500,
"qos": "default|custom|<preset_name>"
}
}
'''Fields''':

* <code>name</code>: Unique tunnel identifier (string, required)
* <code>enabled</code>: Enable/disable tunnel (boolean, default: true)
* <code>password</code>: Tunnel password (string, required)
* <code>mtu</code>: MTU value between 1100-1500 (uint16, default: 1500)
* <code>qos</code>: QoS mode selection (string, default: “default”) - <code>"default"</code>: Use client QoS settings - <code>"custom"</code>: Use custom QoS configuration
* Other values: Use named QoS preset

===Port Forwarding Configuration===
TODO: currently not implemented
{
"enabled": true,
"tunnel": "tunnel_name",
"publicPort": 8080,
"targetIp": "192.168.1.100",
"targetPort": 80,
"description": "Web server forward"
}
'''Fields''':

* <code>enabled</code>: Enable/disable this port forward (boolean)
* <code>tunnel</code>: Associated tunnel name (string)
* <code>publicPort</code>: External port number (uint16)
* <code>targetIp</code>: Internal target IP address (string)
* <code>targetPort</code>: Internal target port (uint16)
* <code>description</code>: Note/description (string, max 1024 chars)
===QoS Configuration===
TODO
===Complete Example===

'''Enable Managed Users (Local Mode)''':
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json"
}
}
'''Remote Mode with Events''':
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json",
"configEndpoint": "https://management.example.com/api/config",
"configAuth": "Bearer abc123universal456",
"eventEndpoint": "https://management.example.com/api/events"
},
"caFile": "/etc/ssl/certs/root-ca.pem"
}
'''Initial Config File''' (<code>/etc/bondix/managed-users.json</code>):
{
"version": 1,
"config": {
"admin@example.com": {
"password": "5e884898da1904719...",
"tunnels": [
{
"config": {
"name": "office-tunnel",
"enabled": true,
"password": "secure123",
"mtu": 1500,
"qos": "default"
}
}
],
"portForwarding": [],
"qos": []
}
}
}
===Error Handling===

'''Common Error Responses''':

* <code>{"result": "error", "error": "already enabled"}</code> - Managed users already active
* <code>401 Unauthorized</code> - Invalid or missing authentication
* <code>403 Forbidden</code> - Invalid current password for change
* <code>500 Internal Server Error</code> - Server-side errors

'''Version Conflicts''':

When remote mode is enabled and version conflicts occur:

* Local changes with higher version take precedence
* Remote changes with higher version are applied
* Synchronization retries automatically

===Password Management Details===

'''Password Storage''':

Passwords stored as SHA256 hashes (OpenSSL 1.x/3.x compatible), no plaintext password storage.

'''Password Reset Flow''':

# User POSTs to <code>/api/forgot-password</code> with email
# Server generates 16-character temporary password
# Event sent to <code>eventEndpoint</code> with <code>eventType: "password_request"</code>
# Temporary password valid for 30 minutes
# Rate-limited to 15 minutes between requests

'''Password Change''':

* Requires current password verification
* New password hashed and stored
* Temporary password cleared on successful change

===Synchronization Timing===

'''Local Mode''':

* Changes saved immediately to config file
* No periodic sync required

'''Remote Mode''':

* Initial fetch on handler startup
* Store sync: Every 5 seconds after changes
* Fetch sync: Every 30 minutes if no pending changes
* Automatic retry on failure__NOINDEX__

Server/User Management

2026-01-22T10:57:01Z

Red: add page; work in progress

(this is a work in progress article for the upcoming 1.26.01 Bondix release. Content is subject to change.)
==Managed User Configuration Documentation==
===Overview===

The Managed User system provides a complete user management solution for the BondingServer, including tunnel management, port forwarding, QoS settings, and optional remote synchronization. This system is designed for multi-tenant scenarios where users need to manage their own tunnels through a dedicated web interface.
===Modes of Operation===

The system operates in two modes:
====Local Mode (Default)====

*Configuration stored in a local JSON file
*No remote synchronization
*Ideal for single-server deployments
*All configuration changes saved locally
====Remote Mode====

*Configuration synchronized with a remote server
*Periodic sync every 30 minutes
*Changes pushed to remote server automatically
*Events sent to webhook endpoint
*Ideal for distributed/multi-server deployments
===Local Configuration File Layout===

While users can be stored in the main server configuration, it’s '''discouraged'''. Using a separate configuration file offers greater flexibility and cleaner separation.

'''Recommended file''': <code>/path/to/managed-users.json</code>

'''Structure''':
{
"version": 1,
"config": {
"user@example.com": {
"password": "sha256_hash",
"tunnels": [
{
"config": {
"name": "office-tunnel",
"enabled": true,
"password": "tunnel_password",
"mtu": 1500,
"qos": "default"
}
}
],
"portForwarding": [],
"qos": []
},
"admin@example.com": {
"password": "sha256_hash",
"tunnels": [
{
"config": {
"name": "main-tunnel",
"enabled": true,
"password": "secure_pass",
"mtu": 1400,
"qos": "custom"
}
}
],
"portForwarding": [],
"qos": {
"classes": [
{
"name": "high-priority",
"priority": 1,
"bandwidth": 1000,
"rules": []
}
]
}
}
}
}
'''Root Fields''':

- <code>version</code>: Configuration version number (uint64, required)

- <code>config</code>: Object containing user configurations keyed by username

'''Per-User Fields''':

- <code>password</code>: SHA256 hash of the user’s password

- <code>tunnels</code>: Array of tunnel configurations

- <code>portForwarding</code>: Array of port forwarding rules ('''currently not implemented''')

- <code>qos</code>: QoS configuration object
===Enabling Managed Users===

'''Action''': <code>enable-user-management</code>

'''Configuration JSON''':
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/path/to/managed-users.json"
},
"caFile": "/etc/ssl/certs/root-ca.pem"
}

{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json"
}
}
'''Settings Object Fields''':

- <code>config</code>: Path to local configuration file (string, required for local mode)

- <code>configEndpoint</code>: Remote sync URL (string, optional)

- <code>configAuth</code>: Authentication token for remote endpoints (string, optional)

- <code>eventEndpoint</code>: Webhook URL for events (string, optional)

- <code>users</code>: Array of initial users (optional, discouraged)

'''SSL/TLS Options''':

- <code>caDirectory</code>: Directory containing CA certificates

- <code>caFile</code>: Single CA file path
===Remote Mode Configuration===

When <code>configEndpoint</code> is specified, the system operates in remote mode:
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json",
"configEndpoint": "https://management.example.com/api/config",
"configAuth": "Bearer universal_auth_token",
"eventEndpoint": "https://management.example.com/api/events"
}
}
'''Remote Sync Behavior''':

1. '''Initial Fetch''': On startup, fetches configuration from remote endpoint

2. '''Periodic Sync''': Every 30 minutes, checks for remote updates

3. '''Change Push''': Every 5 seconds after local changes, syncs to remote

4. '''Version Control''': Uses version numbers to prevent conflicts

'''Event Webhook Events''':

- <code>password_request</code>: Triggered when user requests password reset - Payload includes temporary password for the user

'''Remote Endpoint Requirements''':

- <code>configEndpoint</code> must accept GET for fetch and POST for store

- Both endpoints require <code>Authorization</code> header with configured auth token

- Fetch returns 204 if no newer version exists, 200 with config JSON otherwise
===Web Frontend===

'''Frontend Location''': <code>/user</code>

'''Automatic Redirect''': When user management is enabled, the server automatically redirects requests from <code>/</code> to <code>/user</code>. Use /admin for full access.

The frontend provides:

- User login interface

- Tunnel management dashboard

- Port forwarding configuration

- QoS settings management

- Password change functionality
===API Endpoints===

All endpoints require authentication via Bearer token or universal auth token.
====Authentication Endpoints====

'''POST <code>/api/login</code>'''
// Request
{
"username": "user@example.com",
"password": "password"
}

// Response (200 OK)
{
"token": "session_token",
"user": {
"email": "user@example.com",
"name": "User"
}
}

// Response (401 Unauthorized)

{"allowReset": true} // If eventEndpoint configured

'''POST <code>/api/forgot-password</code>'''
// Request
{
"email": "user@example.com"
}

// Response: 204 No Content (if user exists and eventEndpoint configured)

====Configuration Endpoints====

'''GET <code>/api/config</code>'''
// Response
{
"tunnels": [...],
"portForwarding": [...],
"qos": [...]
}

'''POST <code>/api/config</code>'''

<syntaxhighlight lang="json">// Request - Update any combination of tunnels, port forwarding, or QoS
{
// Request
{
"tunnels": [
{
"config": {
"name": "tunnel_name",
"enabled": true,
"password": "new_password",
"mtu": 1500,
"qos": "default"
}
}
],
"portForwarding": [...],
"qos": [...]
}
// Response
{
"tunnels": [...],
"portForwarding": [...],
"qos": [...]
}
'''Important''': This endpoint is the primary method for updating any configuration. When remote mode is enabled, calling this endpoint triggers the synchronization methods automatically.

'''POST <code>/api/change-password</code>'''
// Request
{
"currentPassword": "old_password",
"newPassword": "new_password"
}

// Response

{"result": "ok"}
====Tunnel Management Endpoints====

'''GET <code>/api/status</code>'''

<syntaxhighlight lang="json">// Response
{
// Response
{
"tunnel": [
{
"name": "tunnel_name",
"status": "connected|disconnected|disabled",
"uptime": 12345,
"clientIp": "10.0.0.1/24",
"gatewayIp": "10.0.0.254",
"channelConnected": 2,
"currentIncoming": 1024,
"currentOutgoing": 2048,
"activeProxyConnections": 1,
"qosName": "default",
"totalIncoming": 1024000,
"totalOutgoing": 2048000,
"environment": "env_name",
"connectedChannels": 2,
"channels": [
{
"status": "connected",
"enabled": true,
"name": "channel_name",
"interface": "eth0",
"address": "10.0.0.1",
"uptime": 3600,
"lastError": "",
"totalOutgoing": 512000,
"totalIncoming": 1024000,
"connectionAttempts": 1,
"connectionType": "TCP",
"stats": {
"currentLatency": 15,
"idleLatency": 10,
"inTransit": 1024,
"packetloss": 0.1
}
}
]
}
]
}

'''POST <code>/api/restart</code>'''
// Request
{
"tunnel": "tunnel_name"
}

// Response

{"result": "ok"}

-----


===7. Universal Authentication Token===

For third-party frontend integration or administrative operations, a universal auth token can be used to impersonate any user.

'''Authentication Method''':

1. Set Authorization header to the configured <code>configAuth</code> token

2. Set <code>X-Username</code> header to the target user’s email

'''Example Request''':

TODO: add request

'''....'''

'''Security Note''': The universal auth token should be kept secure and only used for trusted applications.
===Tunnel Configuration Structure===
{
"config": {
"name": "tunnel_name",
"enabled": true,
"password": "tunnel_password",
"mtu": 1500,
"qos": "default|custom|<preset_name>"
}
}
'''Fields''':

- <code>name</code>: Unique tunnel identifier (string, required)

- <code>enabled</code>: Enable/disable tunnel (boolean, default: true)

- <code>password</code>: Tunnel password (string, required)

- <code>mtu</code>: MTU value between 1100-1500 (uint16, default: 1500)

- <code>qos</code>: QoS mode selection (string, default: “default”) - <code>"default"</code>: Use client QoS settings - <code>"custom"</code>: Use custom QoS configuration

- Other values: Use named QoS preset
===Port Forwarding Configuration===
TODO: currently not implemented
{
"enabled": true,
"tunnel": "tunnel_name",
"publicPort": 8080,
"targetIp": "192.168.1.100",
"targetPort": 80,
"description": "Web server forward"
}
'''Fields''':

- <code>enabled</code>: Enable/disable this port forward (boolean)

- <code>tunnel</code>: Associated tunnel name (string)

- <code>publicPort</code>: External port number (uint16)

- <code>targetIp</code>: Internal target IP address (string)

- <code>targetPort</code>: Internal target port (uint16)

- <code>description</code>: Note/description (string, max 1024 chars)
===QoS Configuration===
{
"classes": [
{
"name": "class_name",
"priority": 1,
"bandwidth": 1000,
"rules": [...]
}
]
}

'''Fields''':

- <code>classes</code>: Array of QoS classes

- <code>name</code>: Class identifier (string)

- <code>priority</code>: Priority level (uint16)

- <code>bandwidth</code>: Bandwidth allocation (uint16)

- <code>rules</code>: Traffic classification rules
===Complete Example===

'''Enable Managed Users (Local Mode)''':
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json"
}
}
'''Remote Mode with Events''':
{
"target": "server",
"action": "enable-user-management",
"settings": {
"config": "/var/lib/bonding/managed-users.json",
"configEndpoint": "https://management.example.com/api/config",
"configAuth": "Bearer abc123universal456",
"eventEndpoint": "https://management.example.com/api/events"
},
"caFile": "/etc/ssl/certs/root-ca.pem"
}
'''Initial Config File''' (<code>/var/lib/bonding/managed-users.json</code>):
{
"version": 1,
"config": {
"admin@example.com": {
"password": "5e884898da1904719...",
"tunnels": [
{
"config": {
"name": "office-tunnel",
"enabled": true,
"password": "secure123",
"mtu": 1500,
"qos": "default"
}
}
],
"portForwarding": [],
"qos": []
}
}
}
===Error Handling===

'''Common Error Responses''':

- <code>{"result": "error", "error": "already enabled"}</code> - Managed users already active

- <code>401 Unauthorized</code> - Invalid or missing authentication

- <code>403 Forbidden</code> - Invalid current password for change

- <code>500 Internal Server Error</code> - Server-side errors

'''Version Conflicts''':

When remote mode is enabled and version conflicts occur:

- Local changes with higher version take precedence

- Remote changes with higher version are applied

- Synchronization retries automatically
===Password Management Details===

'''Password Storage''':

- Passwords stored as SHA256 hashes (OpenSSL 1.x/3.x compatible)

- No plaintext password storage

'''Password Reset Flow''':

1. User POSTs to <code>/api/forgot-password</code> with email

2. Server generates 16-character temporary password

3. Event sent to <code>eventEndpoint</code> with <code>eventType: "password_request"</code>

4. Temporary password valid for 30 minutes

5. Rate-limited to 15 minutes between requests

'''Password Change''':

- Requires current password verification

- New password hashed and stored

- Temporary password cleared on successful change
===Synchronization Timing===

'''Local Mode''':

- Changes saved immediately to config file

- No periodic sync required

'''Remote Mode''':

- Initial fetch on handler startup

- Store sync: Every 5 seconds after changes

- Fetch sync: Every 30 minutes if no pending changes

- Automatic retry on failure

__NOINDEX__

Downloads

2026-01-14T12:53:12Z

Red:

= 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.

'''Recommended Licenses'''
[[File:Recommd-router-list.png|thumb|center]]

'''Current Release Version:''' 1.25.7.2''' '''
{{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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!Download
(RUTOS version)
|-
|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTX_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTX_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTX_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|RUTM
|RUTM08, RUTM09, RUTM10, RUTM11, RUTM50, RUTM51, RUTM52, RUTM54, RUTM59
|[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTM_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTM_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTM_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956
|[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUT9M_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUT9M_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUT9M_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|RUT2M
|RUT200, RUT241, RUT260
|[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUT2M_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUT2M_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUT2M_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|RUTC
|RUTC50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTC_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTC_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTC_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|RUTE
|RUT206, RUT271
|[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTE_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTE_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-RUTE_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|OTD500
|OTD500
|[https://releases.bondix.dev/files/bondixclient-1.25.7.5-OTD5_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-OTD5_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-OTD5_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|ATRM50
|ATRM50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.5-ATRM50_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-ATRM50_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.5-ATRM50_R_00.07.19.4.tar.gz 00.07.19.4]
|}

====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.

===Advantech===
Please contact our support team via our [https://support.bondix.net/ Support Portal].
==Server==

===Current Version (1.25.7.5)===
*[https://releases.bondix.dev/endpoint/install-bondix-server.sh install-bondix-server.sh]
Download and execute this script on your server.

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

===Previous Version (1.24.1.9) ===
'''Note:''' With the release of version 1.25.x, significant changes have been introduced. For users who may need it, we've made the previous version available which continues to receive critical fixes. ''However, please be aware that downgrading from version 1.25.x to this earlier release is not supported''.

*[https://releases.bondix.dev/endpoint/install-bondix-server-1.24.1.9.sh install-bondix-server-1.24.1.9.sh]

We provide only the server component for this version. The client software should always be kept up to date. If you believe you need an older client version, please reach out to us.

==Changelog==

=== 1.25.7.4===
*[Client] Add Support for RutOS 07.18

===1.25.7.3 ===
*Fix QoS mismatching when the only difference in matching rules is DSCP value
*

===1.25.7.2 ===
*[Server] Fix state confusion when SIGHUP was received early during startup
*[Client] Fix client UI breaking when two or more WAN interfaces were created at once after installing the client package.
* [Client] Add Teltonika ATRM50 series

===1.25.7.1 ===
*Fix 'Environment Isolation' filtering incoming responses for legitimate traffic
*Fixed an issue parsing responses from api.bondix.dev if message was too long
*Fix removing certificate tunnel when no timeout was specified
*remove debug message present in all binaries
*Fix client attempting to use other configured servers if CloudLink or QuickConnect code was used

=== 1.25.7 ===
*Resolved a rare issue where malformed SSL communication could trigger a watchdog-initiated restart of the Bondix server process.
* Fixed an issue where disconnecting one channel could inadvertently cause another channel to disconnect within the same environment.
*Server-Tunnel Settings: Disable Transparent Bonding Proxy; users can now disable the transparent Bonding Proxy in environments where it is enabled by default.
*Server-Tunnel Settings: Generate Connection String; added the ability to generate a connection code on the Servers tunnel settings, that simplifies the configuration of Bondix clients.
*Server-Tunnel Settings: Global Packet Size Configuration; introduced a (tunnel) global setting to define the packet size for Bondix payloads across all active channels. (Note: This is not the same as MTU size.)
*Server-Environment Settings: Bind Proxy to Outgoing Interface; ensures that traffic always uses the Bondix server’s outgoing interface, even if the destination network is reachable via another tunnel or environment on the same server. This setting needs to be disabled for LAN-to-LAN traffic.
*Server-Environment Settings: Isolate Environment; allows complete isolation of an environment from incoming traffic. Caution: This will disable TCP port forwarding and the Transparent Bonding Proxy.

===1.25.3===

*[[IPv6|Initial IPv6 support]]
*[[Prometheus|Prometheus Support]]
*New Unified Client UI
*Support for latest Teltonika RUTOS firmwares
*Many bugfixes and performance improvements

=== 1.24.1.9===

*Fixed an issue where a channel disconnect could cause an unrelated channel to disconnect as well

=== 1.24.1.8 ===

*Improved detection for stuck flows
*Fix issue where some outgoing protocol packets would not be sent, which would be reported as lost packets
*Fix interface selection by ignoring channels with unknown latency

''Versions 1.24.1.6 & 1.24.1.7 were just for internal testing and/or have been retracted.''

===1.24.1.5===

*Added support for Teltonika RutOS 07.07.3.
*Previous fix for 'no traffic after last remaining channel disconnect' was incomplete; the issue could still trigger in rare circumstances. Additionally, client and server now have detection mechanisms to identify if the remote side is affected by this or similar issues.

=== 1.24.1.4===
*Added support for Teltonika RUTOS 07.07.1 and 07.06.11
*Fixed "No error message was provided" message in Bondix Client log when using Cloudlink. The message was always shown despite no error being reported. Functionality was unaffected.
===1.24.1.3===
* Fixed a rare crash that could arise in very specific situations when writing data to a socket
*Add environment & Uptime in statistics/SNMP
*Fixed an issue where certificate based tunnels were not removed despite set-tunnel-autoremove being configured, when the initial tunnel handshake never completed
* add tunnel name as parameter when calling tunnel-tapconnect/tunnel-tapdisconnect
*In some place an argument would be passed to OpenSSL without checking whether the argument is valid, potentially resulting in a crash.
===1.24.1.2===
*Fixed an issue where traffic would no longer pass through the tunnel after the last remaining channel disconnected and reconnected without triggering a tunnel reset.
*Fixed an issue on Teltonika where DSCP values in the QoS editor would not be saved.
*On Teltonika, the client will now automatically restart after 5 minutes of tunnel downtime. The behavior of the underlying “set-restart-on-failure" configuration command has been fixed.
*Added metrics for connection attempts and active BondingProxy connections. The number of active proxy connections can now be observed in the monitor.
*Added support for Teltonika RutOS 07.06.6.
==Release Notes==
*[[release-notes/202308|August 2023]]
*[[release-notes/202306|June 2023]]
*[[release-notes/2023-05|May 2023]]
*[[release-notes/2023-04|April 2023]]
*[[release-notes/2023-01|January 2023]]
*[[release-notes/2022-12|December 2022]]
*[[release-notes/2022-11|November 2022]]
*[[release-notes/2022-10|October 2022]]
*[[release-notes/2022-09|September 2022]]
{| class="wikitable"

|}

Downloads

2026-01-14T11:07:04Z

Red:

= 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.

'''Recommended Licenses'''
[[File:Recommd-router-list.png|thumb|center]]

'''Current Release Version:''' 1.25.7.2''' '''
{{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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!Download
(RUTOS version)
|-
|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTX_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|RUTM
|RUTM08, RUTM09, RUTM10, RUTM11, RUTM50, RUTM51, RUTM52, RUTM54, RUTM59
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTM_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT9M_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|RUT2M
|RUT200, RUT241, RUT260
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT2M_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|RUTC
|RUTC50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTC_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|RUTE
|RUT206, RUT271
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTE_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|OTD500
|OTD500
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-OTD5_R_00.07.19.4.tar.gz 00.07.19.4]
|-
|ATRM50
|ATRM50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.20.1.tar.gz 00.07.20.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-ATRM50_R_00.07.19.4.tar.gz 00.07.19.4]
|}

====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.

===Advantech===
Please contact our support team via our [https://support.bondix.net/ Support Portal].
==Server==

===Current Version (1.25.7.5)===
*[https://releases.bondix.dev/endpoint/install-bondix-server.sh install-bondix-server.sh]
Download and execute this script on your server.

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

===Previous Version (1.24.1.9) ===
'''Note:''' With the release of version 1.25.x, significant changes have been introduced. For users who may need it, we've made the previous version available which continues to receive critical fixes. ''However, please be aware that downgrading from version 1.25.x to this earlier release is not supported''.

*[https://releases.bondix.dev/endpoint/install-bondix-server-1.24.1.9.sh install-bondix-server-1.24.1.9.sh]

We provide only the server component for this version. The client software should always be kept up to date. If you believe you need an older client version, please reach out to us.

==Changelog==

=== 1.25.7.4===
*[Client] Add Support for RutOS 07.18

===1.25.7.3 ===
*Fix QoS mismatching when the only difference in matching rules is DSCP value
*

===1.25.7.2 ===
*[Server] Fix state confusion when SIGHUP was received early during startup
*[Client] Fix client UI breaking when two or more WAN interfaces were created at once after installing the client package.
* [Client] Add Teltonika ATRM50 series

===1.25.7.1 ===
*Fix 'Environment Isolation' filtering incoming responses for legitimate traffic
*Fixed an issue parsing responses from api.bondix.dev if message was too long
*Fix removing certificate tunnel when no timeout was specified
*remove debug message present in all binaries
*Fix client attempting to use other configured servers if CloudLink or QuickConnect code was used

=== 1.25.7 ===
*Resolved a rare issue where malformed SSL communication could trigger a watchdog-initiated restart of the Bondix server process.
* Fixed an issue where disconnecting one channel could inadvertently cause another channel to disconnect within the same environment.
*Server-Tunnel Settings: Disable Transparent Bonding Proxy; users can now disable the transparent Bonding Proxy in environments where it is enabled by default.
*Server-Tunnel Settings: Generate Connection String; added the ability to generate a connection code on the Servers tunnel settings, that simplifies the configuration of Bondix clients.
*Server-Tunnel Settings: Global Packet Size Configuration; introduced a (tunnel) global setting to define the packet size for Bondix payloads across all active channels. (Note: This is not the same as MTU size.)
*Server-Environment Settings: Bind Proxy to Outgoing Interface; ensures that traffic always uses the Bondix server’s outgoing interface, even if the destination network is reachable via another tunnel or environment on the same server. This setting needs to be disabled for LAN-to-LAN traffic.
*Server-Environment Settings: Isolate Environment; allows complete isolation of an environment from incoming traffic. Caution: This will disable TCP port forwarding and the Transparent Bonding Proxy.

===1.25.3===

*[[IPv6|Initial IPv6 support]]
*[[Prometheus|Prometheus Support]]
*New Unified Client UI
*Support for latest Teltonika RUTOS firmwares
*Many bugfixes and performance improvements

=== 1.24.1.9===

*Fixed an issue where a channel disconnect could cause an unrelated channel to disconnect as well

=== 1.24.1.8 ===

*Improved detection for stuck flows
*Fix issue where some outgoing protocol packets would not be sent, which would be reported as lost packets
*Fix interface selection by ignoring channels with unknown latency

''Versions 1.24.1.6 & 1.24.1.7 were just for internal testing and/or have been retracted.''

===1.24.1.5===

*Added support for Teltonika RutOS 07.07.3.
*Previous fix for 'no traffic after last remaining channel disconnect' was incomplete; the issue could still trigger in rare circumstances. Additionally, client and server now have detection mechanisms to identify if the remote side is affected by this or similar issues.

=== 1.24.1.4===
*Added support for Teltonika RUTOS 07.07.1 and 07.06.11
*Fixed "No error message was provided" message in Bondix Client log when using Cloudlink. The message was always shown despite no error being reported. Functionality was unaffected.
===1.24.1.3===
* Fixed a rare crash that could arise in very specific situations when writing data to a socket
*Add environment & Uptime in statistics/SNMP
*Fixed an issue where certificate based tunnels were not removed despite set-tunnel-autoremove being configured, when the initial tunnel handshake never completed
* add tunnel name as parameter when calling tunnel-tapconnect/tunnel-tapdisconnect
*In some place an argument would be passed to OpenSSL without checking whether the argument is valid, potentially resulting in a crash.
===1.24.1.2===
*Fixed an issue where traffic would no longer pass through the tunnel after the last remaining channel disconnected and reconnected without triggering a tunnel reset.
*Fixed an issue on Teltonika where DSCP values in the QoS editor would not be saved.
*On Teltonika, the client will now automatically restart after 5 minutes of tunnel downtime. The behavior of the underlying “set-restart-on-failure" configuration command has been fixed.
*Added metrics for connection attempts and active BondingProxy connections. The number of active proxy connections can now be observed in the monitor.
*Added support for Teltonika RutOS 07.06.6.
==Release Notes==
*[[release-notes/202308|August 2023]]
*[[release-notes/202306|June 2023]]
*[[release-notes/2023-05|May 2023]]
*[[release-notes/2023-04|April 2023]]
*[[release-notes/2023-01|January 2023]]
*[[release-notes/2022-12|December 2022]]
*[[release-notes/2022-11|November 2022]]
*[[release-notes/2022-10|October 2022]]
*[[release-notes/2022-09|September 2022]]
{| class="wikitable"

|}

Releases/advantech

2025-12-09T11:34:09Z

Red:

Bondix Releases

== Advantech ==

=== LR77 (all models) ===

=== ICR-2834 ===

=== ICR-2734 ===

=== ICR-2431 ===

=== ICR-2531 ===

=== SmartStart ===

=== SmartFlex ===

=== SmartMotion ===

=== ICR-3231 (all models) ===

=== ICR-4401 ===

=== ICR-4434 ===

=== ICR-4453 ===

Client/Releases/advantech

2025-12-09T11:33:57Z

Red:

Manuals/Sane-client-tel-rutx12-v0702

2025-12-09T11:33:42Z

Red:

''[[Main_Page|Start]] > [[Main_Page#Client|Client]] > [[Manuals/Sane-client-tel-rutx12-v0702|Teltonika Version 7.02.x]]''
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: []

[[Category:7.04.03]]
[[Category:Server]]

Manuals/Sane-client-tel-rutx12-v0702

2025-12-09T11:32:49Z

Red:

''[[Main_Page|Start]] > [[Main_Page#Client|Client]] > [[Manuals/Sane-client-tel-rutx12-v0702|Teltonika Version 7.02.x]]''
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 S.A.NE 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: []

[[Category:7.04.03]]
[[Category:Server]]

FAQs

2025-12-09T11:32:05Z

Red:

''[[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/Client

2025-12-09T11:31:35Z

Red:

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: []

Manuals/Client

2025-12-09T11:30:50Z

Red:

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 S.A.NE 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: []

Client/StaticRoutes

2025-12-09T11:29:34Z

Red:

[[Category:Client]]
== 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.

Monitor 7.02.x

2025-12-09T11:29:22Z

Red:

[[Category:Manual]]
[[Category:Advanced Settings]]
[[Category:Traffic Monitor]]
=== 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''”.}}

Architecture

2025-12-09T11:29:12Z

Red:

[[Category:General]]
''[[Main_Page|Start]] > [[Main_Page#Basics|Basics]] > [[Architecture]]''

== Bondix System Overview ==

=== Introduction ===
The need for reliable connectivity with high bandwidths is continuously growing. Bondix was developed to ensure reliable connectivity for all applications such as voice, video and data transmission. This applies to mobile as well as stationary deployments.

This simple and efficient software solution can be installed on different platforms to enable these WAN aggregation functions. The Bondix software implements bonding (aggregation) of, load balancing between, and seamless handover across, different WAN interfaces and WAN providers. It thus provides a highly available overall connection that keeps you online without interruption.

=== Application ===
To increase the throughput or availability of access to remote applications, the use of two or more connections is often chosen. These can be fixed network or wireless (Fiber, DSL, WiFi, cellular, satellite) connections, or a combination of these. The question is how to manage the use of these different connections efficiently and easily. This is where the Bondix software comes in, ensuring a highly available connection and optimal throughput.

==== High availability and bonding ====
With a second connection via an alternative cellular network operator (or another WAN medium such as WiFi or satellite), the total bandwidth available for even a single TCP/IP connection can be increased, as well as the uptime. Line failures or network problems at service providers can thus be mitigated. With Bondix, WAN scheduling is based on a wide range of policies and presets, which are available in the Bondix Client and can be selected by the user based on his requirements. With its very efficient bonding and wide feature set, the Bondix software enables a highly resilient and cost-effective virtual uplink for mobile as well as fixed locations.

'''Bondix technology offers three options here:'''
{| class="wikitable"
| Seamless backup || Different WAN uplinks are available, but only the primary uplink is used by the running application at a time. In the event of an primary uplink-failure, the system automatically switches to the next available interface/uplink seamlessly without interrupting or disconnecting existing connections.
|-
| Load balancing with seamless handover || The data of the application is distributed evenly over the available WAN uplinks. The maximum available bandwidth for an application is limited by the available bandwidth of its assigned uplink. If one uplink fails, affected traffic is distributed to a different uplink.

However, there is a possibility that an application may be degraded in performance after switching due to the now lower available bandwidth.
|-
| Bonding (WAN aggregation) || The optimal solution for the simultaneous use of several WAN uplink is Bondix WAN Bonding (aggregation). With bonding, the user application benefits from the aggregated bandwidth from the available WAN uplinks. Bondix optimizes the distribution of traffic flows across the various uplinks. This is particularly advantageous if the bandwidth of a single connection cannot provide the bandwidth required by the application.
|}

=== Additional Features ===
{| class="wikitable"
| Bondix Packet Duplication || For low-latency real-time applications, this option reduces jitter and loss by replicating the user’s packet-flow on two or more available WAN uplinks.
|-
| Bondix Bonding Proxy || A specialized optimization for TCP connections that allows higher data throughput where uplink characteristics are vastly different (e.g. Satellite and 4G).
|-
| Bondix Latency Smoothing || By constantly monitoring the performance and latency of each uplink, Bondix bonding ensures that a single uplink Is never saturated, ensuring stable latency. Interactive, low-bandwidth streams are sent over the fastest link, while bulk traffic Is distributed over all uplinks.
|-
| Optimal use of available WANs || You can easily add additional uplinks to enhance throughput of your fixed internet uplink during times of peak demand. Bondix will automatically utilize additional uplinks as soon as more bandwidth is required and keep them on stand-by to save cost when bandwidth demands recedes.
|}

=== Architecture ===
The Bondix architecture consists of the Bondix client and the Bondix server (relay). The client software is installed on the router (CPE) and allows all existing WAN interfaces to be combined into a virtual tunnel. This tunnel can be established via any type of WAN medium and uses the Bondix server as a relay, from which the data is then forwarded to the inter- or intranet.

The following example provides an overview of a common router that sets up a Bondix bonded tunnel via multiple WAN uplinks:

<gallery perrow="1" mode="packed" widths="800" heights="294">
File:Bondix-architecture.png|Bondix Architecture
</gallery>

== Security ==
The Bondix software has several built-in security mechanisms:
{| class="wikitable"
| Certificate-Based Authentication || Bondix supports certificate-based authentication for both client & server. If a router is lost or stolen, it can be permanently excluded in just a few steps.
|-
| VPN Support || Unlike other WAN bonding solutions in the market and due to its unique architecture, Bondix does not introduce a proprietary VPN to effectively bundle data traffic but has excellent support for Industry leading VPN solutions like IPSec, OpenVPN & Wireguard.
|-
| Server Geo-Redundancy || Bondix supports server redundancy. In case of a backend failure, clients can be configured to automatically switch between multiple endpoints, keeping downtime to an absolute minimum.
|}

== Management ==
Bondix has built-in tools to monitor the status of the clients, gateway, and all WAN connections in operation.

'''Bondix Realtime Monitoring'''
<gallery perrow="1" mode="packed" widths="652" heights="393">
File:Bondix-architecture-monitor.png|All status information can be queried via command-line interface, a custom API or SNMP and can be easily integrated in existing monitoring platforms like Nagios or comparable products.
</gallery>

== Hardware Platform ==
The Bondix client software is intended as a hardware-agnostic multi-WAN router operating system and is already available today on the following platforms:

* Teltonika
** RUTX Series (incl. RUTX50)
** RUT950/955
** RUT360
** RUT240
* AnyRover
* OpenWRT

On the server side, the software is delivered as an Open Virtual Appliance (OVA), which can be installed on a local server as well as in the cloud.

Client/Quickstart

2025-12-09T11:24:43Z

Red:

Basic instructions for installing the client on your RUTX12.

It is recommend reset all router settings before you start the installation
1) Please check that the RUTX12 is running the version RUTX_R_00.02.06.1. If not, download and install it from here:
https://wiki.teltonika-networks.com/wikibase/images/6/62/RUTX_R_00.02.06.1_WEBUI.bin
2) Download the latest Client here:

https://releases.bondix.dev/files/saneclient-armv7-202112031459-84c5b697.ipk

3) Go to Packet Manager and install the Bondix client

Please also check that no Teltonika load balancing functionality is active on the router since this will have a massive impact on the performance:

Also make sure that you have configured DNS forwarding to 8.8.8.8 and 9.9.9.9 to receive DNS through the tunnel:

The general settings for the Bondix client should be set as follows:

"Tunnel" and "Password" should contain the credentials you received via email.

Please leave the “Backup Server” empty for now since this would require identical tunnel names on both servers to work

Once you entered the credentials please press "save and apply" and "restart service" afterwards

You can enter the IP of the Backup server here to is you have created one.

Tunnel Preset "Bonding"

WAN interfaces

If you are using 2 LTE and you want them used evenly, please use the following settings:

If you do changes here, please always press "save and apply" and "update interface configuration". If you are also changing priority settings, please also press "restart service" so the new rules are also applied correctly on the server

Please check that the advanced settings are set as follows:

To enable the local Bondix debug Web interface

Attention: Settings here are not persistent and for debugging only. The Web interface does not work with Apple Safari, please use Chrome, Egde or Firefox instead

Enable debug Web interface to "on"

Debug listener IP (your IP of the Teltonika Web interface, standard is 192.168.1.1)

Define a listener port (I always use "8088"

Define a password (I always us something like "123456" since it is only local

press "save and apply"

press "restart service" in the general settings

If everything was set correctly you should get this page:

Here you enter your tunnel name and the password you set for the debug Web interface:

Press "Senden" to log into the Bondix Web interface

It will show you a graphical overview of the data traffic and connection status of the connected links

Server

2025-12-09T11:24:08Z

Red:

[[Category:Server]]
[[Category:Manual]]
[[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]

Quality of Service

2025-12-09T11:23:42Z

Red:

==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''.

Manuals/Server

2025-12-09T11:23:00Z

Red:

== 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-24.04) ===
⚠️ '''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>

Server Certificates with LetsEncrypt

2025-12-09T11:22:42Z

Red:

[[Category:Server]]
[[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 outdated

2025-12-09T11:22:21Z

Red:

The Bondix Server is a universal Linux service for x86_64 architectures (other architectures available on request). Thanks to static compilation, there are no special host operating system requirements such as specific LibC versions - the only requirement is kernel support for virtual tun/tap network interfaces.

== Requirements ==

=== Resources ===
The resource requirement is based on the peak total throughput of the installation and the number of simultaneous tunnel connections. This formula can be used as a rule of thumb for the required memory:
Memory requirement (megabytes) = Bandwidth(Mbit) / 2 + TunnelCount * 5

Example: An installation of 100 tunnels should guarantee 50 Mbit/sec for each instance at full load. The peak bandwidth would thus be 100 * 50 Mbit = 5000 Mbit/sec. Using the above formula, this results in a memory requirement of approx. 3 gigabytes.
In addition to memory, the number of CPU cores is also critical. Bondix SANE Server distributes incoming tunnels to different CPU cores for load balancing. While the maximum throughput per CPU core depends on the hardware used, 500 - 1000 Mbit can be taken as a conservative estimate.

Note: These assumptions for storage do not take into account requirements for the host operating system, other services, and the like. Requirements for storage space are negligible.

=== Public Ports ===
Bondix SANE Server requires a publicly accessible TCP port (default 443, but freely selectable) and at least one UDP port - the number of UDP ports depends on the environments configured.

== Installation ==
...

== Configuration ==
The default installation script comes with a default configuration that enables the webinterface, where environment and tunnel configuration can be done. However, configuration is very versatile and can be customized.

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

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

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

== Environments ==
Environments are a collection of tunnels that share certain resources, like packet buffers, thread, UDP port and virtual network interfaces.
[[File:Server Environment Settings.png|center|frame]]

== Running ==
The software can be run in the shell using <code>/opt/bondix/server/saneserver</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/saneserver.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"
|-
| <s>useMMSG</s>|| uses useMMSG linux socket API to send & receive multiple UDP packets at once. This improves performance under load, while stable there are some corner cases which can trigger error messages in the log.
|-
| <s>bondingProxy</s>|| Enables the TCP [[Bonding Proxy]].
|}

== SNMP ==
The server comes with a net-snmp extension that implements the provided MIB. In order to use it with netsnmp, add this to your <code>/etc/snmp/snmpd.conf</code>:
pass_persist .1.3.6.1.3.45265 /opt/bondix/server/bxsnmp

Advanced Settings

2025-12-09T11:21:57Z

Red:

==== 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.
|}

Server Licensing

2025-12-09T11:21:35Z

Red:

== 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/Routes

2025-12-09T11:21:07Z

Red:

[[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!

Layer 2

2025-12-09T11:20:51Z

Red:

[[Category:Manual]]
[[Category:7.02.x]]
==== 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]]

Server/Configuration

2025-12-09T11:20:29Z

Red:

== 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>

Starlink

2025-12-09T11:20:15Z

Red:

[[Category:Client]]
[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.

General Teltonika Router Settings

2025-12-09T11:19:47Z

Red:

[[Category:7.02.x]]
== 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]]

Main Page

2025-12-09T11:19:32Z

Red:

{{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 Essential Cloud How-To]] Setup Bondix Essential Cloud 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.

=== 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]]

== 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]

Manuals

2025-12-09T11:18:54Z

Red:

Find here manuals on different versions of the Bondix Client and Server.

=== Bondix Client ===

* Teltonika
** RUTX12:
*** [[Manuals/Sane-client-tel-rutx12-v0702|Version 07.02]]
*** [[Manuals/Sane-client-tel-rutx12-v0206|Version 02.06]]
** RUT9
*** [[Manuals/Sane-client-tel-rut9-v0701|Version 07.01]]

=== Bondix Server ===

* [[Manuals/Sane-server-v01|Version 1]], February 2022

Client/Quickstart

2025-12-09T11:18:17Z

Red:

Basic instructions for installing the client on your RUTX12.

It is recommend reset all router settings before you start the installation
1) Please check that the RUTX12 is running the version RUTX_R_00.02.06.1. If not, download and install it from here:
https://wiki.teltonika-networks.com/wikibase/images/6/62/RUTX_R_00.02.06.1_WEBUI.bin
2) Download the latest Client here:

https://releases.bondix.dev/files/saneclient-armv7-202112031459-84c5b697.ipk

3) Go to Packet Manager and install the S.A.NE client

Please also check that no Teltonika load balancing functionality is active on the router since this will have a massive impact on the performance:

Also make sure that you have configured DNS forwarding to 8.8.8.8 and 9.9.9.9 to receive DNS through the tunnel:

The general settings for the Bondix client should be set as follows:

"Tunnel" and "Password" should contain the credentials you received via email.

Please leave the “Backup Server” empty for now since this would require identical tunnel names on both servers to work

Once you entered the credentials please press "save and apply" and "restart service" afterwards

You can enter the IP of the Backup server here to is you have created one.

Tunnel Preset "Bonding"

WAN interfaces

If you are using 2 LTE and you want them used evenly, please use the following settings:

If you do changes here, please always press "save and apply" and "update interface configuration". If you are also changing priority settings, please also press "restart service" so the new rules are also applied correctly on the server

Please check that the advanced settings are set as follows:

To enable the local Bondix debug Web interface

Attention: Settings here are not persistent and for debugging only. The Web interface does not work with Apple Safari, please use Chrome, Egde or Firefox instead

Enable debug Web interface to "on"

Debug listener IP (your IP of the Teltonika Web interface, standard is 192.168.1.1)

Define a listener port (I always use "8088"

Define a password (I always us something like "123456" since it is only local

press "save and apply"

press "restart service" in the general settings

If everything was set correctly you should get this page:

Here you enter your tunnel name and the password you set for the debug Web interface:

Press "Senden" to log into the Bondix Web interface

It will show you a graphical overview of the data traffic and connection status of the connected links

Manuals/Sane-server-v01

2025-12-09T11:16:59Z

Red:

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

== 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 Bondix:
* Google Chrome
* MS Edge
* Mozilla Firefox

=== Updating the 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) ===
⚠️ '''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 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 S.ANE 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 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 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. 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 will 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]

Interfaces

2025-12-09T11:15:01Z

Red:

[[Category:WAN Interfaces]]
[[Category:Manual]]
[[Category:7.02.x]]
===== 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]]

Server Capacity

2025-12-09T11:14:28Z

Red:

[[Category:Server]]
== 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.

Advanced Settings

2025-12-09T11:04:13Z

Red:

==== 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 S.A.NE’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 S.A.NE 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.
|}

Client Installation

2025-12-09T11:03:58Z

Red:

[[Category:Manual]]
[[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.

Status

2025-12-09T11:03:30Z

Red:

[[Category:Teltonika]]
[[Category:Manual]]
[[Category:7.02.x]]
=== 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.
|}

Configuration Mode

2025-12-09T11:02:57Z

Red:

[[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''”.}}

Release-notes/202306

2025-12-09T11:01:39Z

Red:

== BONDIX RELEASE NOTES June 2023 ==
Bondix Clients are downward compatible, meaning newer Client builds and/or Server versions may be operated with each other and still function well, but in order to fully benefit from all new features to their full extend though, we recommend you update your Bondix S.A.NE server to the latest version. Please find more information on how to do that in our [[Manuals/Sane-server-v01|Bondix S.A.NE Server Manual]].

You can find and download the latest Bondix S.A.NE for your device here: [https://www.bondixintelligence.com/downloads Bondix S.A.NE Releases].

=== NEW FEATURES ===
==== Dark Mode ====
The Bondix S.A.NE Server web interface now comes with a dark mode that is hopefully more pleasing to the eyes of those that generally surf the dark side of life. Whether dark mode is used or not depends on the system settings.

[[File:Screenshot-server-dark-mode.png|frame|center]]

=== IMPROVEMENTS ===
Server
* More advanced SNMP: The ''bxsnmp'' SNMP utility and MIB has been improved in quality and number of features.

=== FIXES ===
Server
* An issue potentially causing a premature socket close in the bonding proxy was fixed.

== Download release notes as PDF ==
[https://226d8a3e-9b65-453b-93bd-7875e511be8d.usrfiles.com/ugd/226d8a_dab8e2805ecb467e8890042b3c6b1e64.pdf June 2023]

Manuals

2025-12-09T11:01:18Z

Red:

Find here manuals on different versions of the Bondix S.A.NE Client and Server.

=== Bondix Client ===

* Teltonika
** RUTX12:
*** [[Manuals/Sane-client-tel-rutx12-v0702|Version 07.02]]
*** [[Manuals/Sane-client-tel-rutx12-v0206|Version 02.06]]
** RUT9
*** [[Manuals/Sane-client-tel-rut9-v0701|Version 07.01]]

=== Bondix Server ===

* [[Manuals/Sane-server-v01|Version 1]], February 2022

Downloads

2025-11-24T11:07:07Z

Red:

= 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.

'''Recommended Licenses'''
[[File:Recommd-router-list.png|thumb|center]]

'''Current Release Version:''' 1.25.7.2''' '''
{{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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!Download
(RUTOS version)
|-
|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.19.1.tar.gz 00.07.19.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTX_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTM
|RUTM08, RUTM09, RUTM10, RUTM11, RUTM50, RUTM51, RUTM52, RUTM54, RUTM59
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.19.1.tar.gz 00.07.19.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTM_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.19.1.tar.gz 00.07.19.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT9M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT2M
|RUT200, RUT241, RUT260
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.19.1.tar.gz 00.07.19.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT2M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTC
|RUTC50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.19.1.tar.gz 00.07.19.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTC_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTE
|RUT206, RUT271
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.19.1.tar.gz 00.07.19.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTE_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|OTD500
|OTD500
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.19.1.tar.gz 00.07.19.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-OTD5_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|ATRM50
|ATRM50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.19.1.tar.gz 00.07.19.1]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-ATRM50_R_00.07.17.5.tar.gz 00.07.17.5]
|}

====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.

===Advantech===
Please contact our support team via our [https://support.bondix.net/ Support Portal].
==Server==

===Current Version (1.25.7.4)===
*[https://releases.bondix.dev/endpoint/install-bondix-server.sh install-bondix-server.sh]
Download and execute this script on your server.

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

===Previous Version (1.24.1.9) ===
'''Note:''' With the release of version 1.25.x, significant changes have been introduced. For users who may need it, we've made the previous version available which continues to receive critical fixes. ''However, please be aware that downgrading from version 1.25.x to this earlier release is not supported''.

*[https://releases.bondix.dev/endpoint/install-bondix-server-1.24.1.9.sh install-bondix-server-1.24.1.9.sh]

We provide only the server component for this version. The client software should always be kept up to date. If you believe you need an older client version, please reach out to us.

==Changelog==

=== 1.25.7.4===
*[Client] Add Support for RutOS 07.18

===1.25.7.3 ===
*Fix QoS mismatching when the only difference in matching rules is DSCP value
*

===1.25.7.2 ===
*[Server] Fix state confusion when SIGHUP was received early during startup
*[Client] Fix client UI breaking when two or more WAN interfaces were created at once after installing the client package.
* [Client] Add Teltonika ATRM50 series

===1.25.7.1 ===
*Fix 'Environment Isolation' filtering incoming responses for legitimate traffic
*Fixed an issue parsing responses from api.bondix.dev if message was too long
*Fix removing certificate tunnel when no timeout was specified
*remove debug message present in all binaries
*Fix client attempting to use other configured servers if CloudLink or QuickConnect code was used

=== 1.25.7 ===
*Resolved a rare issue where malformed SSL communication could trigger a watchdog-initiated restart of the Bondix server process.
* Fixed an issue where disconnecting one channel could inadvertently cause another channel to disconnect within the same environment.
*Server-Tunnel Settings: Disable Transparent Bonding Proxy; users can now disable the transparent Bonding Proxy in environments where it is enabled by default.
*Server-Tunnel Settings: Generate Connection String; added the ability to generate a connection code on the Servers tunnel settings, that simplifies the configuration of Bondix clients.
*Server-Tunnel Settings: Global Packet Size Configuration; introduced a (tunnel) global setting to define the packet size for Bondix payloads across all active channels. (Note: This is not the same as MTU size.)
*Server-Environment Settings: Bind Proxy to Outgoing Interface; ensures that traffic always uses the Bondix server’s outgoing interface, even if the destination network is reachable via another tunnel or environment on the same server. This setting needs to be disabled for LAN-to-LAN traffic.
*Server-Environment Settings: Isolate Environment; allows complete isolation of an environment from incoming traffic. Caution: This will disable TCP port forwarding and the Transparent Bonding Proxy.

===1.25.3===

*[[IPv6|Initial IPv6 support]]
*[[Prometheus|Prometheus Support]]
*New Unified Client UI
*Support for latest Teltonika RUTOS firmwares
*Many bugfixes and performance improvements

=== 1.24.1.9===

*Fixed an issue where a channel disconnect could cause an unrelated channel to disconnect as well

=== 1.24.1.8 ===

*Improved detection for stuck flows
*Fix issue where some outgoing protocol packets would not be sent, which would be reported as lost packets
*Fix interface selection by ignoring channels with unknown latency

''Versions 1.24.1.6 & 1.24.1.7 were just for internal testing and/or have been retracted.''

===1.24.1.5===

*Added support for Teltonika RutOS 07.07.3.
*Previous fix for 'no traffic after last remaining channel disconnect' was incomplete; the issue could still trigger in rare circumstances. Additionally, client and server now have detection mechanisms to identify if the remote side is affected by this or similar issues.

=== 1.24.1.4===
*Added support for Teltonika RUTOS 07.07.1 and 07.06.11
*Fixed "No error message was provided" message in Bondix Client log when using Cloudlink. The message was always shown despite no error being reported. Functionality was unaffected.
===1.24.1.3===
* Fixed a rare crash that could arise in very specific situations when writing data to a socket
*Add environment & Uptime in statistics/SNMP
*Fixed an issue where certificate based tunnels were not removed despite set-tunnel-autoremove being configured, when the initial tunnel handshake never completed
* add tunnel name as parameter when calling tunnel-tapconnect/tunnel-tapdisconnect
*In some place an argument would be passed to OpenSSL without checking whether the argument is valid, potentially resulting in a crash.
===1.24.1.2===
*Fixed an issue where traffic would no longer pass through the tunnel after the last remaining channel disconnected and reconnected without triggering a tunnel reset.
*Fixed an issue on Teltonika where DSCP values in the QoS editor would not be saved.
*On Teltonika, the client will now automatically restart after 5 minutes of tunnel downtime. The behavior of the underlying “set-restart-on-failure" configuration command has been fixed.
*Added metrics for connection attempts and active BondingProxy connections. The number of active proxy connections can now be observed in the monitor.
*Added support for Teltonika RutOS 07.06.6.
==Release Notes==
*[[release-notes/202308|August 2023]]
*[[release-notes/202306|June 2023]]
*[[release-notes/2023-05|May 2023]]
*[[release-notes/2023-04|April 2023]]
*[[release-notes/2023-01|January 2023]]
*[[release-notes/2022-12|December 2022]]
*[[release-notes/2022-11|November 2022]]
*[[release-notes/2022-10|October 2022]]
*[[release-notes/2022-09|September 2022]]
{| class="wikitable"

|}

Downloads

2025-11-11T09:50:09Z

Red: /* 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.

'''Recommended Licenses'''
[[File:Recommd-router-list.png|thumb|center]]

'''Current Release Version:''' 1.25.7.2''' '''
{{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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!Download
(RUTOS version)
|-
|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.19.tar.gz 00.07.19]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTX_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTM
|RUTM08, RUTM09, RUTM10, RUTM11, RUTM50, RUTM51, RUTM52, RUTM54, RUTM59
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.19.tar.gz 00.07.19]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTM_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.19.tar.gz 00.07.19]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT9M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT2M
|RUT200, RUT241, RUT260
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.19.tar.gz 00.07.19]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT2M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTC
|RUTC50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.19.tar.gz 00.07.19]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTC_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTE
|RUT206, RUT271
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.19.tar.gz 00.07.19]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTE_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|OTD500
|OTD500
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.19.tar.gz 00.07.19]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-OTD5_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|ATRM50
|ATRM50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.19.tar.gz 00.07.19]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.18.3.tar.gz 00.07.18.3]<nowiki> | </nowiki>[https://releases.bondix.dev/files/bondixclient-1.25.7.3-ATRM50_R_00.07.17.5.tar.gz 00.07.17.5]
|}

====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.

===Advantech===
Please contact our support team via our [https://support.bondix.net/ Support Portal].
==Server==

===Current Version (1.25.7.4)===
*[https://releases.bondix.dev/endpoint/install-bondix-server.sh install-bondix-server.sh]
Download and execute this script on your server.

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

===Previous Version (1.24.1.9) ===
'''Note:''' With the release of version 1.25.x, significant changes have been introduced. For users who may need it, we've made the previous version available which continues to receive critical fixes. ''However, please be aware that downgrading from version 1.25.x to this earlier release is not supported''.

*[https://releases.bondix.dev/endpoint/install-bondix-server-1.24.1.9.sh install-bondix-server-1.24.1.9.sh]

We provide only the server component for this version. The client software should always be kept up to date. If you believe you need an older client version, please reach out to us.

==Changelog==

=== 1.25.7.4===
*[Client] Add Support for RutOS 07.18

===1.25.7.3 ===
*Fix QoS mismatching when the only difference in matching rules is DSCP value
*

===1.25.7.2 ===
*[Server] Fix state confusion when SIGHUP was received early during startup
*[Client] Fix client UI breaking when two or more WAN interfaces were created at once after installing the client package.
* [Client] Add Teltonika ATRM50 series

===1.25.7.1 ===
*Fix 'Environment Isolation' filtering incoming responses for legitimate traffic
*Fixed an issue parsing responses from api.bondix.dev if message was too long
*Fix removing certificate tunnel when no timeout was specified
*remove debug message present in all binaries
*Fix client attempting to use other configured servers if CloudLink or QuickConnect code was used

=== 1.25.7 ===
*Resolved a rare issue where malformed SSL communication could trigger a watchdog-initiated restart of the Bondix server process.
* Fixed an issue where disconnecting one channel could inadvertently cause another channel to disconnect within the same environment.
*Server-Tunnel Settings: Disable Transparent Bonding Proxy; users can now disable the transparent Bonding Proxy in environments where it is enabled by default.
*Server-Tunnel Settings: Generate Connection String; added the ability to generate a connection code on the Servers tunnel settings, that simplifies the configuration of Bondix clients.
*Server-Tunnel Settings: Global Packet Size Configuration; introduced a (tunnel) global setting to define the packet size for Bondix payloads across all active channels. (Note: This is not the same as MTU size.)
*Server-Environment Settings: Bind Proxy to Outgoing Interface; ensures that traffic always uses the Bondix server’s outgoing interface, even if the destination network is reachable via another tunnel or environment on the same server. This setting needs to be disabled for LAN-to-LAN traffic.
*Server-Environment Settings: Isolate Environment; allows complete isolation of an environment from incoming traffic. Caution: This will disable TCP port forwarding and the Transparent Bonding Proxy.

===1.25.3===

*[[IPv6|Initial IPv6 support]]
*[[Prometheus|Prometheus Support]]
*New Unified Client UI
*Support for latest Teltonika RUTOS firmwares
*Many bugfixes and performance improvements

=== 1.24.1.9===

*Fixed an issue where a channel disconnect could cause an unrelated channel to disconnect as well

=== 1.24.1.8 ===

*Improved detection for stuck flows
*Fix issue where some outgoing protocol packets would not be sent, which would be reported as lost packets
*Fix interface selection by ignoring channels with unknown latency

''Versions 1.24.1.6 & 1.24.1.7 were just for internal testing and/or have been retracted.''

===1.24.1.5===

*Added support for Teltonika RutOS 07.07.3.
*Previous fix for 'no traffic after last remaining channel disconnect' was incomplete; the issue could still trigger in rare circumstances. Additionally, client and server now have detection mechanisms to identify if the remote side is affected by this or similar issues.

=== 1.24.1.4===
*Added support for Teltonika RUTOS 07.07.1 and 07.06.11
*Fixed "No error message was provided" message in Bondix Client log when using Cloudlink. The message was always shown despite no error being reported. Functionality was unaffected.
===1.24.1.3===
* Fixed a rare crash that could arise in very specific situations when writing data to a socket
*Add environment & Uptime in statistics/SNMP
*Fixed an issue where certificate based tunnels were not removed despite set-tunnel-autoremove being configured, when the initial tunnel handshake never completed
* add tunnel name as parameter when calling tunnel-tapconnect/tunnel-tapdisconnect
*In some place an argument would be passed to OpenSSL without checking whether the argument is valid, potentially resulting in a crash.
===1.24.1.2===
*Fixed an issue where traffic would no longer pass through the tunnel after the last remaining channel disconnected and reconnected without triggering a tunnel reset.
*Fixed an issue on Teltonika where DSCP values in the QoS editor would not be saved.
*On Teltonika, the client will now automatically restart after 5 minutes of tunnel downtime. The behavior of the underlying “set-restart-on-failure" configuration command has been fixed.
*Added metrics for connection attempts and active BondingProxy connections. The number of active proxy connections can now be observed in the monitor.
*Added support for Teltonika RutOS 07.06.6.
==Release Notes==
*[[release-notes/202308|August 2023]]
*[[release-notes/202306|June 2023]]
*[[release-notes/2023-05|May 2023]]
*[[release-notes/2023-04|April 2023]]
*[[release-notes/2023-01|January 2023]]
*[[release-notes/2022-12|December 2022]]
*[[release-notes/2022-11|November 2022]]
*[[release-notes/2022-10|October 2022]]
*[[release-notes/2022-09|September 2022]]
{| class="wikitable"

|}

Downloads

2025-11-11T09:46:29Z

Red:

= 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.

'''Recommended Licenses'''
[[File:Recommd-router-list.png|thumb|center]]

'''Current Release Version:''' 1.25.7.2''' '''
{{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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!Download
(RUTOS version)
|-
|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.19.tar.gz 00.07.19][https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.18.3.tar.gz 00.07.18.3][https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTX_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTM
|RUTM08, RUTM09, RUTM10, RUTM11, RUTM50, RUTM51, RUTM52, RUTM54, RUTM59
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.19.tar.gz 00.07.19][https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.18.3.tar.gz 00.07.18.3][https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTM_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.19.tar.gz 00.07.19][https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.18.3.tar.gz 00.07.18.3][https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT9M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT2M
|RUT200, RUT241, RUT260
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.19.tar.gz 00.07.19][https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.18.3.tar.gz 00.07.18.3][https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT2M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTC
|RUTC50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.19.tar.gz 00.07.19][https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.18.3.tar.gz 00.07.18.3][https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTC_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTE
|RUT206, RUT271
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.19.tar.gz 00.07.19][https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.18.3.tar.gz 00.07.18.3][https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTE_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|OTD500
|OTD500
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.19.tar.gz 00.07.19][https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.18.3.tar.gz 00.07.18.3][https://releases.bondix.dev/files/bondixclient-1.25.7.3-OTD5_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|ATRM50
|ATRM50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.19.tar.gz 00.07.19][https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.18.3.tar.gz 00.07.18.3][https://releases.bondix.dev/files/bondixclient-1.25.7.3-ATRM50_R_00.07.17.5.tar.gz 00.07.17.5]
|}

====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.

===Advantech===
Please contact our support team via our [https://support.bondix.net/ Support Portal].
==Server==

===Current Version (1.25.7.4)===
*[https://releases.bondix.dev/endpoint/install-bondix-server.sh install-bondix-server.sh]
Download and execute this script on your server.

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

===Previous Version (1.24.1.9) ===
'''Note:''' With the release of version 1.25.x, significant changes have been introduced. For users who may need it, we've made the previous version available which continues to receive critical fixes. ''However, please be aware that downgrading from version 1.25.x to this earlier release is not supported''.

*[https://releases.bondix.dev/endpoint/install-bondix-server-1.24.1.9.sh install-bondix-server-1.24.1.9.sh]

We provide only the server component for this version. The client software should always be kept up to date. If you believe you need an older client version, please reach out to us.

==Changelog==

=== 1.25.7.4===
*[Client] Add Support for RutOS 07.18

===1.25.7.3 ===
*Fix QoS mismatching when the only difference in matching rules is DSCP value
*

===1.25.7.2 ===
*[Server] Fix state confusion when SIGHUP was received early during startup
*[Client] Fix client UI breaking when two or more WAN interfaces were created at once after installing the client package.
* [Client] Add Teltonika ATRM50 series

===1.25.7.1 ===
*Fix 'Environment Isolation' filtering incoming responses for legitimate traffic
*Fixed an issue parsing responses from api.bondix.dev if message was too long
*Fix removing certificate tunnel when no timeout was specified
*remove debug message present in all binaries
*Fix client attempting to use other configured servers if CloudLink or QuickConnect code was used

=== 1.25.7 ===
*Resolved a rare issue where malformed SSL communication could trigger a watchdog-initiated restart of the Bondix server process.
* Fixed an issue where disconnecting one channel could inadvertently cause another channel to disconnect within the same environment.
*Server-Tunnel Settings: Disable Transparent Bonding Proxy; users can now disable the transparent Bonding Proxy in environments where it is enabled by default.
*Server-Tunnel Settings: Generate Connection String; added the ability to generate a connection code on the Servers tunnel settings, that simplifies the configuration of Bondix clients.
*Server-Tunnel Settings: Global Packet Size Configuration; introduced a (tunnel) global setting to define the packet size for Bondix payloads across all active channels. (Note: This is not the same as MTU size.)
*Server-Environment Settings: Bind Proxy to Outgoing Interface; ensures that traffic always uses the Bondix server’s outgoing interface, even if the destination network is reachable via another tunnel or environment on the same server. This setting needs to be disabled for LAN-to-LAN traffic.
*Server-Environment Settings: Isolate Environment; allows complete isolation of an environment from incoming traffic. Caution: This will disable TCP port forwarding and the Transparent Bonding Proxy.

===1.25.3===

*[[IPv6|Initial IPv6 support]]
*[[Prometheus|Prometheus Support]]
*New Unified Client UI
*Support for latest Teltonika RUTOS firmwares
*Many bugfixes and performance improvements

=== 1.24.1.9===

*Fixed an issue where a channel disconnect could cause an unrelated channel to disconnect as well

=== 1.24.1.8 ===

*Improved detection for stuck flows
*Fix issue where some outgoing protocol packets would not be sent, which would be reported as lost packets
*Fix interface selection by ignoring channels with unknown latency

''Versions 1.24.1.6 & 1.24.1.7 were just for internal testing and/or have been retracted.''

===1.24.1.5===

*Added support for Teltonika RutOS 07.07.3.
*Previous fix for 'no traffic after last remaining channel disconnect' was incomplete; the issue could still trigger in rare circumstances. Additionally, client and server now have detection mechanisms to identify if the remote side is affected by this or similar issues.

=== 1.24.1.4===
*Added support for Teltonika RUTOS 07.07.1 and 07.06.11
*Fixed "No error message was provided" message in Bondix Client log when using Cloudlink. The message was always shown despite no error being reported. Functionality was unaffected.
===1.24.1.3===
* Fixed a rare crash that could arise in very specific situations when writing data to a socket
*Add environment & Uptime in statistics/SNMP
*Fixed an issue where certificate based tunnels were not removed despite set-tunnel-autoremove being configured, when the initial tunnel handshake never completed
* add tunnel name as parameter when calling tunnel-tapconnect/tunnel-tapdisconnect
*In some place an argument would be passed to OpenSSL without checking whether the argument is valid, potentially resulting in a crash.
===1.24.1.2===
*Fixed an issue where traffic would no longer pass through the tunnel after the last remaining channel disconnected and reconnected without triggering a tunnel reset.
*Fixed an issue on Teltonika where DSCP values in the QoS editor would not be saved.
*On Teltonika, the client will now automatically restart after 5 minutes of tunnel downtime. The behavior of the underlying “set-restart-on-failure" configuration command has been fixed.
*Added metrics for connection attempts and active BondingProxy connections. The number of active proxy connections can now be observed in the monitor.
*Added support for Teltonika RutOS 07.06.6.
==Release Notes==
*[[release-notes/202308|August 2023]]
*[[release-notes/202306|June 2023]]
*[[release-notes/2023-05|May 2023]]
*[[release-notes/2023-04|April 2023]]
*[[release-notes/2023-01|January 2023]]
*[[release-notes/2022-12|December 2022]]
*[[release-notes/2022-11|November 2022]]
*[[release-notes/2022-10|October 2022]]
*[[release-notes/2022-09|September 2022]]
{| class="wikitable"

|}

Downloads

2025-11-11T09:45:15Z

Red:

= 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.

'''Recommended Licenses'''
[[File:Recommd-router-list.png|thumb|center]]

'''Current Release Version:''' 1.25.7.2''' '''
{{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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!Download
(RUTOS version)
|-
|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.19.tar.gz 00.07.19]
[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTX_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTM
|RUTM08, RUTM09, RUTM10, RUTM11, RUTM50, RUTM51, RUTM52, RUTM54, RUTM59
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.19.tar.gz 00.07.19]
[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTM_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.19.tar.gz 00.07.19]
[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT9M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT2M
|RUT200, RUT241, RUT260
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.19.tar.gz 00.07.19]
[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT2M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTC
|RUTC50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.19.tar.gz 00.07.19]
[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTC_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTE
|RUT206, RUT271
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.19.tar.gz 00.07.19]
[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTE_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|OTD500
|OTD500
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.19.tar.gz 00.07.19]
[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-OTD5_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|ATRM50
|ATRM50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.19.tar.gz 00.07.19]
[https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-ATRM50_R_00.07.17.5.tar.gz 00.07.17.5]
|}

====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.

===Advantech===
Please contact our support team via our [https://support.bondix.net/ Support Portal].
==Server==

===Current Version (1.25.7.4)===
*[https://releases.bondix.dev/endpoint/install-bondix-server.sh install-bondix-server.sh]
Download and execute this script on your server.

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

===Previous Version (1.24.1.9) ===
'''Note:''' With the release of version 1.25.x, significant changes have been introduced. For users who may need it, we've made the previous version available which continues to receive critical fixes. ''However, please be aware that downgrading from version 1.25.x to this earlier release is not supported''.

*[https://releases.bondix.dev/endpoint/install-bondix-server-1.24.1.9.sh install-bondix-server-1.24.1.9.sh]

We provide only the server component for this version. The client software should always be kept up to date. If you believe you need an older client version, please reach out to us.

==Changelog==

=== 1.25.7.4===
*[Client] Add Support for RutOS 07.18

===1.25.7.3 ===
*Fix QoS mismatching when the only difference in matching rules is DSCP value
*

===1.25.7.2 ===
*[Server] Fix state confusion when SIGHUP was received early during startup
*[Client] Fix client UI breaking when two or more WAN interfaces were created at once after installing the client package.
* [Client] Add Teltonika ATRM50 series

===1.25.7.1 ===
*Fix 'Environment Isolation' filtering incoming responses for legitimate traffic
*Fixed an issue parsing responses from api.bondix.dev if message was too long
*Fix removing certificate tunnel when no timeout was specified
*remove debug message present in all binaries
*Fix client attempting to use other configured servers if CloudLink or QuickConnect code was used

=== 1.25.7 ===
*Resolved a rare issue where malformed SSL communication could trigger a watchdog-initiated restart of the Bondix server process.
* Fixed an issue where disconnecting one channel could inadvertently cause another channel to disconnect within the same environment.
*Server-Tunnel Settings: Disable Transparent Bonding Proxy; users can now disable the transparent Bonding Proxy in environments where it is enabled by default.
*Server-Tunnel Settings: Generate Connection String; added the ability to generate a connection code on the Servers tunnel settings, that simplifies the configuration of Bondix clients.
*Server-Tunnel Settings: Global Packet Size Configuration; introduced a (tunnel) global setting to define the packet size for Bondix payloads across all active channels. (Note: This is not the same as MTU size.)
*Server-Environment Settings: Bind Proxy to Outgoing Interface; ensures that traffic always uses the Bondix server’s outgoing interface, even if the destination network is reachable via another tunnel or environment on the same server. This setting needs to be disabled for LAN-to-LAN traffic.
*Server-Environment Settings: Isolate Environment; allows complete isolation of an environment from incoming traffic. Caution: This will disable TCP port forwarding and the Transparent Bonding Proxy.

===1.25.3===

*[[IPv6|Initial IPv6 support]]
*[[Prometheus|Prometheus Support]]
*New Unified Client UI
*Support for latest Teltonika RUTOS firmwares
*Many bugfixes and performance improvements

=== 1.24.1.9===

*Fixed an issue where a channel disconnect could cause an unrelated channel to disconnect as well

=== 1.24.1.8 ===

*Improved detection for stuck flows
*Fix issue where some outgoing protocol packets would not be sent, which would be reported as lost packets
*Fix interface selection by ignoring channels with unknown latency

''Versions 1.24.1.6 & 1.24.1.7 were just for internal testing and/or have been retracted.''

===1.24.1.5===

*Added support for Teltonika RutOS 07.07.3.
*Previous fix for 'no traffic after last remaining channel disconnect' was incomplete; the issue could still trigger in rare circumstances. Additionally, client and server now have detection mechanisms to identify if the remote side is affected by this or similar issues.

=== 1.24.1.4===
*Added support for Teltonika RUTOS 07.07.1 and 07.06.11
*Fixed "No error message was provided" message in Bondix Client log when using Cloudlink. The message was always shown despite no error being reported. Functionality was unaffected.
===1.24.1.3===
* Fixed a rare crash that could arise in very specific situations when writing data to a socket
*Add environment & Uptime in statistics/SNMP
*Fixed an issue where certificate based tunnels were not removed despite set-tunnel-autoremove being configured, when the initial tunnel handshake never completed
* add tunnel name as parameter when calling tunnel-tapconnect/tunnel-tapdisconnect
*In some place an argument would be passed to OpenSSL without checking whether the argument is valid, potentially resulting in a crash.
===1.24.1.2===
*Fixed an issue where traffic would no longer pass through the tunnel after the last remaining channel disconnected and reconnected without triggering a tunnel reset.
*Fixed an issue on Teltonika where DSCP values in the QoS editor would not be saved.
*On Teltonika, the client will now automatically restart after 5 minutes of tunnel downtime. The behavior of the underlying “set-restart-on-failure" configuration command has been fixed.
*Added metrics for connection attempts and active BondingProxy connections. The number of active proxy connections can now be observed in the monitor.
*Added support for Teltonika RutOS 07.06.6.
==Release Notes==
*[[release-notes/202308|August 2023]]
*[[release-notes/202306|June 2023]]
*[[release-notes/2023-05|May 2023]]
*[[release-notes/2023-04|April 2023]]
*[[release-notes/2023-01|January 2023]]
*[[release-notes/2022-12|December 2022]]
*[[release-notes/2022-11|November 2022]]
*[[release-notes/2022-10|October 2022]]
*[[release-notes/2022-09|September 2022]]
{| class="wikitable"

|}

Downloads

2025-11-03T09:38:57Z

Red:

= 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.

'''Recommended Licenses'''
[[File:Recommd-router-list.png|thumb|center]]

'''Current Release Version:''' 1.25.7.2''' '''
{{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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!Download
(RUTOS version)
|-
|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTX_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTM
|RUTM08, RUTM09, RUTM10, RUTM11, RUTM50, RUTM51, RUTM52, RUTM54, RUTM59
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTM_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT9M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT2M
|RUT200, RUT241, RUT260
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT2M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTC
|RUTC50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTC_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTE
|RUT206, RUT271
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTE_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|OTD500
|OTD500
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-OTD5_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|ATRM50
|ATRM50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-ATRM50_R_00.07.17.5.tar.gz 00.07.17.5]
|}

==== 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.

===Advantech===
Please contact our support team via our [https://support.bondix.net/ Support Portal].
== Server==

=== Current Version (1.25.7.3) ===
*[https://releases.bondix.dev/endpoint/install-bondix-server.sh install-bondix-server.sh]
Download and execute this script on your server.

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

=== Previous Version (1.24.1.9) ===
'''Note:''' With the release of version 1.25.x, significant changes have been introduced. For users who may need it, we've made the previous version available which continues to receive critical fixes. ''However, please be aware that downgrading from version 1.25.x to this earlier release is not supported''.

* [https://releases.bondix.dev/endpoint/install-bondix-server-1.24.1.9.sh install-bondix-server-1.24.1.9.sh]

We provide only the server component for this version. The client software should always be kept up to date. If you believe you need an older client version, please reach out to us.

==Changelog==

=== 1.25.7.4 ===
* [Client] Add Support for RutOS 07.18

=== 1.25.7.3 ===
* Fix QoS mismatching when the only difference in matching rules is DSCP value
*

=== 1.25.7.2 ===
* [Server] Fix state confusion when SIGHUP was received early during startup
* [Client] Fix client UI breaking when two or more WAN interfaces were created at once after installing the client package.
* [Client] Add Teltonika ATRM50 series

=== 1.25.7.1 ===
* Fix 'Environment Isolation' filtering incoming responses for legitimate traffic
* Fixed an issue parsing responses from api.bondix.dev if message was too long
* Fix removing certificate tunnel when no timeout was specified
* remove debug message present in all binaries
* Fix client attempting to use other configured servers if CloudLink or QuickConnect code was used

=== 1.25.7 ===
* Resolved a rare issue where malformed SSL communication could trigger a watchdog-initiated restart of the Bondix server process.
* Fixed an issue where disconnecting one channel could inadvertently cause another channel to disconnect within the same environment.
* Server-Tunnel Settings: Disable Transparent Bonding Proxy; users can now disable the transparent Bonding Proxy in environments where it is enabled by default.
* Server-Tunnel Settings: Generate Connection String; added the ability to generate a connection code on the Servers tunnel settings, that simplifies the configuration of Bondix clients.
* Server-Tunnel Settings: Global Packet Size Configuration; introduced a (tunnel) global setting to define the packet size for Bondix payloads across all active channels. (Note: This is not the same as MTU size.)
* Server-Environment Settings: Bind Proxy to Outgoing Interface; ensures that traffic always uses the Bondix server’s outgoing interface, even if the destination network is reachable via another tunnel or environment on the same server. This setting needs to be disabled for LAN-to-LAN traffic.
* Server-Environment Settings: Isolate Environment; allows complete isolation of an environment from incoming traffic. Caution: This will disable TCP port forwarding and the Transparent Bonding Proxy.

=== 1.25.3 ===

* [[IPv6|Initial IPv6 support]]
* [[Prometheus|Prometheus Support]]
* New Unified Client UI
* Support for latest Teltonika RUTOS firmwares
* Many bugfixes and performance improvements

=== 1.24.1.9 ===

* Fixed an issue where a channel disconnect could cause an unrelated channel to disconnect as well

=== 1.24.1.8 ===

* Improved detection for stuck flows
* Fix issue where some outgoing protocol packets would not be sent, which would be reported as lost packets
* Fix interface selection by ignoring channels with unknown latency

''Versions 1.24.1.6 & 1.24.1.7 were just for internal testing and/or have been retracted.''

=== 1.24.1.5 ===

* Added support for Teltonika RutOS 07.07.3.
* Previous fix for 'no traffic after last remaining channel disconnect' was incomplete; the issue could still trigger in rare circumstances. Additionally, client and server now have detection mechanisms to identify if the remote side is affected by this or similar issues.

===1.24.1.4===
*Added support for Teltonika RUTOS 07.07.1 and 07.06.11
* Fixed "No error message was provided" message in Bondix Client log when using Cloudlink. The message was always shown despite no error being reported. Functionality was unaffected.
===1.24.1.3===
*Fixed a rare crash that could arise in very specific situations when writing data to a socket
* Add environment & Uptime in statistics/SNMP
* Fixed an issue where certificate based tunnels were not removed despite set-tunnel-autoremove being configured, when the initial tunnel handshake never completed
*add tunnel name as parameter when calling tunnel-tapconnect/tunnel-tapdisconnect
*In some place an argument would be passed to OpenSSL without checking whether the argument is valid, potentially resulting in a crash.
=== 1.24.1.2===
* Fixed an issue where traffic would no longer pass through the tunnel after the last remaining channel disconnected and reconnected without triggering a tunnel reset.
*Fixed an issue on Teltonika where DSCP values in the QoS editor would not be saved.
*On Teltonika, the client will now automatically restart after 5 minutes of tunnel downtime. The behavior of the underlying “set-restart-on-failure" configuration command has been fixed.
*Added metrics for connection attempts and active BondingProxy connections. The number of active proxy connections can now be observed in the monitor.
*Added support for Teltonika RutOS 07.06.6.
==Release Notes==
*[[release-notes/202308|August 2023]]
*[[release-notes/202306|June 2023]]
*[[release-notes/2023-05|May 2023]]
*[[release-notes/2023-04|April 2023]]
*[[release-notes/2023-01|January 2023]]
*[[release-notes/2022-12|December 2022]]
*[[release-notes/2022-11|November 2022]]
*[[release-notes/2022-10|October 2022]]
*[[release-notes/2022-09|September 2022]]
{| class="wikitable"

|}

Downloads

2025-11-03T09:38:27Z

Red:

= 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.

'''Recommended Licenses'''
[[File:Recommd-router-list.png|thumb|center]]

'''Current Release Version:''' 1.25.7.2''' '''
{{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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!Download
(RUTOS version)
|-
|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.18.3.tar.gz 00.07.18.6]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTX_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTM
|RUTM08, RUTM09, RUTM10, RUTM11, RUTM50, RUTM51, RUTM52, RUTM54, RUTM59
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTM_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT9M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT2M
|RUT200, RUT241, RUT260
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT2M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTC
|RUTC50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTC_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTE
|RUT206, RUT271
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTE_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|OTD500
|OTD500
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-OTD5_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|ATRM50
|ATRM50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-ATRM50_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-ATRM50_R_00.07.17.5.tar.gz 00.07.17.5]
|}

==== 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.

===Advantech===
Please contact our support team via our [https://support.bondix.net/ Support Portal].
== Server==

=== Current Version (1.25.7.3) ===
*[https://releases.bondix.dev/endpoint/install-bondix-server.sh install-bondix-server.sh]
Download and execute this script on your server.

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

=== Previous Version (1.24.1.9) ===
'''Note:''' With the release of version 1.25.x, significant changes have been introduced. For users who may need it, we've made the previous version available which continues to receive critical fixes. ''However, please be aware that downgrading from version 1.25.x to this earlier release is not supported''.

* [https://releases.bondix.dev/endpoint/install-bondix-server-1.24.1.9.sh install-bondix-server-1.24.1.9.sh]

We provide only the server component for this version. The client software should always be kept up to date. If you believe you need an older client version, please reach out to us.

==Changelog==

=== 1.25.7.4 ===
* [Client] Add Support for RutOS 07.18

=== 1.25.7.3 ===
* Fix QoS mismatching when the only difference in matching rules is DSCP value
*

=== 1.25.7.2 ===
* [Server] Fix state confusion when SIGHUP was received early during startup
* [Client] Fix client UI breaking when two or more WAN interfaces were created at once after installing the client package.
* [Client] Add Teltonika ATRM50 series

=== 1.25.7.1 ===
* Fix 'Environment Isolation' filtering incoming responses for legitimate traffic
* Fixed an issue parsing responses from api.bondix.dev if message was too long
* Fix removing certificate tunnel when no timeout was specified
* remove debug message present in all binaries
* Fix client attempting to use other configured servers if CloudLink or QuickConnect code was used

=== 1.25.7 ===
* Resolved a rare issue where malformed SSL communication could trigger a watchdog-initiated restart of the Bondix server process.
* Fixed an issue where disconnecting one channel could inadvertently cause another channel to disconnect within the same environment.
* Server-Tunnel Settings: Disable Transparent Bonding Proxy; users can now disable the transparent Bonding Proxy in environments where it is enabled by default.
* Server-Tunnel Settings: Generate Connection String; added the ability to generate a connection code on the Servers tunnel settings, that simplifies the configuration of Bondix clients.
* Server-Tunnel Settings: Global Packet Size Configuration; introduced a (tunnel) global setting to define the packet size for Bondix payloads across all active channels. (Note: This is not the same as MTU size.)
* Server-Environment Settings: Bind Proxy to Outgoing Interface; ensures that traffic always uses the Bondix server’s outgoing interface, even if the destination network is reachable via another tunnel or environment on the same server. This setting needs to be disabled for LAN-to-LAN traffic.
* Server-Environment Settings: Isolate Environment; allows complete isolation of an environment from incoming traffic. Caution: This will disable TCP port forwarding and the Transparent Bonding Proxy.

=== 1.25.3 ===

* [[IPv6|Initial IPv6 support]]
* [[Prometheus|Prometheus Support]]
* New Unified Client UI
* Support for latest Teltonika RUTOS firmwares
* Many bugfixes and performance improvements

=== 1.24.1.9 ===

* Fixed an issue where a channel disconnect could cause an unrelated channel to disconnect as well

=== 1.24.1.8 ===

* Improved detection for stuck flows
* Fix issue where some outgoing protocol packets would not be sent, which would be reported as lost packets
* Fix interface selection by ignoring channels with unknown latency

''Versions 1.24.1.6 & 1.24.1.7 were just for internal testing and/or have been retracted.''

=== 1.24.1.5 ===

* Added support for Teltonika RutOS 07.07.3.
* Previous fix for 'no traffic after last remaining channel disconnect' was incomplete; the issue could still trigger in rare circumstances. Additionally, client and server now have detection mechanisms to identify if the remote side is affected by this or similar issues.

===1.24.1.4===
*Added support for Teltonika RUTOS 07.07.1 and 07.06.11
* Fixed "No error message was provided" message in Bondix Client log when using Cloudlink. The message was always shown despite no error being reported. Functionality was unaffected.
===1.24.1.3===
*Fixed a rare crash that could arise in very specific situations when writing data to a socket
* Add environment & Uptime in statistics/SNMP
* Fixed an issue where certificate based tunnels were not removed despite set-tunnel-autoremove being configured, when the initial tunnel handshake never completed
*add tunnel name as parameter when calling tunnel-tapconnect/tunnel-tapdisconnect
*In some place an argument would be passed to OpenSSL without checking whether the argument is valid, potentially resulting in a crash.
=== 1.24.1.2===
* Fixed an issue where traffic would no longer pass through the tunnel after the last remaining channel disconnected and reconnected without triggering a tunnel reset.
*Fixed an issue on Teltonika where DSCP values in the QoS editor would not be saved.
*On Teltonika, the client will now automatically restart after 5 minutes of tunnel downtime. The behavior of the underlying “set-restart-on-failure" configuration command has been fixed.
*Added metrics for connection attempts and active BondingProxy connections. The number of active proxy connections can now be observed in the monitor.
*Added support for Teltonika RutOS 07.06.6.
==Release Notes==
*[[release-notes/202308|August 2023]]
*[[release-notes/202306|June 2023]]
*[[release-notes/2023-05|May 2023]]
*[[release-notes/2023-04|April 2023]]
*[[release-notes/2023-01|January 2023]]
*[[release-notes/2022-12|December 2022]]
*[[release-notes/2022-11|November 2022]]
*[[release-notes/2022-10|October 2022]]
*[[release-notes/2022-09|September 2022]]
{| class="wikitable"

|}

Downloads

2025-11-03T09:27:45Z

Red:

= 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.

'''Recommended Licenses'''
[[File:Recommd-router-list.png|thumb|center]]

'''Current Release Version:''' 1.25.7.2''' '''
{{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==
===Teltonika Routers===
====Packages====
{| class="wikitable"
|+
!Model Series
!Supported Routers
!Download
(RUTOS version)
|-
|RUTX
|RUTX08, RUTX09, RUTX10, RUTX11, RUTX12, RUTX14, RUTX50, RUTXR1
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTX_R_00.07.18.3.tar.gz 00.07.18.6]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTX_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTM
|RUTM08, RUTM09, RUTM10, RUTM11, RUTM50, RUTM51, RUTM52, RUTM54, RUTM59
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTM_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTM_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT9M
|RUT901, RUT906, RUT951, RUT956
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT9M_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT9M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUT2M
|RUT200, RUT241, RUT260
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUT2M_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUT2M_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTC
|RUTC50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTC_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTC_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|RUTE
|RUT206, RUT271
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-RUTE_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-RUTE_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|OTD500
|OTD500
|[https://releases.bondix.dev/files/bondixclient-1.25.7.4-OTD5_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.3-OTD5_R_00.07.17.5.tar.gz 00.07.17.5]
|-
|ATRM50
|ATRM50
|[https://releases.bondix.dev/files/bondixclient-1.25.7.2-ATRM50_R_00.07.18.3.tar.gz 00.07.18.3]
[https://releases.bondix.dev/files/bondixclient-1.25.7.2-ATRM50_R_00.07.17.5.tar.gz 00.07.17.5]
|}

==== 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.

===Advantech===
Please contact our support team via our [https://support.bondix.net/ Support Portal].
== Server==

=== Current Version (1.25.7.3) ===
*[https://releases.bondix.dev/endpoint/install-bondix-server.sh install-bondix-server.sh]
Download and execute this script on your server.

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

=== Previous Version (1.24.1.9) ===
'''Note:''' With the release of version 1.25.x, significant changes have been introduced. For users who may need it, we've made the previous version available which continues to receive critical fixes. ''However, please be aware that downgrading from version 1.25.x to this earlier release is not supported''.

* [https://releases.bondix.dev/endpoint/install-bondix-server-1.24.1.9.sh install-bondix-server-1.24.1.9.sh]

We provide only the server component for this version. The client software should always be kept up to date. If you believe you need an older client version, please reach out to us.

==Changelog==

=== 1.25.7.4 ===
* [Client] Add Support for RutOS 07.18

=== 1.25.7.3 ===
* Fix QoS mismatching when the only difference in matching rules is DSCP value
*

=== 1.25.7.2 ===
* [Server] Fix state confusion when SIGHUP was received early during startup
* [Client] Fix client UI breaking when two or more WAN interfaces were created at once after installing the client package.
* [Client] Add Teltonika ATRM50 series

=== 1.25.7.1 ===
* Fix 'Environment Isolation' filtering incoming responses for legitimate traffic
* Fixed an issue parsing responses from api.bondix.dev if message was too long
* Fix removing certificate tunnel when no timeout was specified
* remove debug message present in all binaries
* Fix client attempting to use other configured servers if CloudLink or QuickConnect code was used

=== 1.25.7 ===
* Resolved a rare issue where malformed SSL communication could trigger a watchdog-initiated restart of the Bondix server process.
* Fixed an issue where disconnecting one channel could inadvertently cause another channel to disconnect within the same environment.
* Server-Tunnel Settings: Disable Transparent Bonding Proxy; users can now disable the transparent Bonding Proxy in environments where it is enabled by default.
* Server-Tunnel Settings: Generate Connection String; added the ability to generate a connection code on the Servers tunnel settings, that simplifies the configuration of Bondix clients.
* Server-Tunnel Settings: Global Packet Size Configuration; introduced a (tunnel) global setting to define the packet size for Bondix payloads across all active channels. (Note: This is not the same as MTU size.)
* Server-Environment Settings: Bind Proxy to Outgoing Interface; ensures that traffic always uses the Bondix server’s outgoing interface, even if the destination network is reachable via another tunnel or environment on the same server. This setting needs to be disabled for LAN-to-LAN traffic.
* Server-Environment Settings: Isolate Environment; allows complete isolation of an environment from incoming traffic. Caution: This will disable TCP port forwarding and the Transparent Bonding Proxy.

=== 1.25.3 ===

* [[IPv6|Initial IPv6 support]]
* [[Prometheus|Prometheus Support]]
* New Unified Client UI
* Support for latest Teltonika RUTOS firmwares
* Many bugfixes and performance improvements

=== 1.24.1.9 ===

* Fixed an issue where a channel disconnect could cause an unrelated channel to disconnect as well

=== 1.24.1.8 ===

* Improved detection for stuck flows
* Fix issue where some outgoing protocol packets would not be sent, which would be reported as lost packets
* Fix interface selection by ignoring channels with unknown latency

''Versions 1.24.1.6 & 1.24.1.7 were just for internal testing and/or have been retracted.''

=== 1.24.1.5 ===

* Added support for Teltonika RutOS 07.07.3.
* Previous fix for 'no traffic after last remaining channel disconnect' was incomplete; the issue could still trigger in rare circumstances. Additionally, client and server now have detection mechanisms to identify if the remote side is affected by this or similar issues.

===1.24.1.4===
*Added support for Teltonika RUTOS 07.07.1 and 07.06.11
* Fixed "No error message was provided" message in Bondix Client log when using Cloudlink. The message was always shown despite no error being reported. Functionality was unaffected.
===1.24.1.3===
*Fixed a rare crash that could arise in very specific situations when writing data to a socket
* Add environment & Uptime in statistics/SNMP
* Fixed an issue where certificate based tunnels were not removed despite set-tunnel-autoremove being configured, when the initial tunnel handshake never completed
*add tunnel name as parameter when calling tunnel-tapconnect/tunnel-tapdisconnect
*In some place an argument would be passed to OpenSSL without checking whether the argument is valid, potentially resulting in a crash.
=== 1.24.1.2===
* Fixed an issue where traffic would no longer pass through the tunnel after the last remaining channel disconnected and reconnected without triggering a tunnel reset.
*Fixed an issue on Teltonika where DSCP values in the QoS editor would not be saved.
*On Teltonika, the client will now automatically restart after 5 minutes of tunnel downtime. The behavior of the underlying “set-restart-on-failure" configuration command has been fixed.
*Added metrics for connection attempts and active BondingProxy connections. The number of active proxy connections can now be observed in the monitor.
*Added support for Teltonika RutOS 07.06.6.
==Release Notes==
*[[release-notes/202308|August 2023]]
*[[release-notes/202306|June 2023]]
*[[release-notes/2023-05|May 2023]]
*[[release-notes/2023-04|April 2023]]
*[[release-notes/2023-01|January 2023]]
*[[release-notes/2022-12|December 2022]]
*[[release-notes/2022-11|November 2022]]
*[[release-notes/2022-10|October 2022]]
*[[release-notes/2022-09|September 2022]]
{| class="wikitable"

|}