Bondix Wiki - User contributions [en]

Transparent Bonding Proxy

2026-03-12T07:39:23Z

Christian:

[[Category:General]]
== Transparent Bonding Proxy ==
Transparent Bonding Proxy (TBP) is a extension that allows Bonding Proxy to establlish connections using the client's original IP. Without TBP, connections utilizing Bonding Proxy will always use the server's default IP address, even if subnets are properly routed to a client.

=== Prerequisites ===
TBP only works with server routes and masquerading disabled on the client.
[[File:Tbp-prerequisites-1.png|thumb|Where to find the masquerading option in a Teltonika router]]
[[File:Tbp-prerequisites-2.png|thumb|Masquerading turned off]]

SANE server uses IP_TRANSPARENT to bind to non-local IP addresses, which required CAP_ADMIN capabilities. For proper operation, we must identify traffic that matches our Bonding Proxy connections:
# iptables -t mangle -N DIVERT
# iptables -t mangle -A PREROUTING -p tcp -m socket -j DIVERT
# iptables -t mangle -A DIVERT -j MARK --set-mark 1
# iptables -t mangle -A DIVERT -j ACCEPT
Then, create a routing table that defines your routed subnet(s) as local
# ip rule add fwmark 1 lookup 100
# ip route add local 0.0.0.0/0 dev lo table 100
0.0.0.0/0 allows any IP to be used. While this also works, it has security implications - add your routed subnets instead to minimize risks.

Currently, TBP will be activated for any proxy connection initiated by a client with a routed IP.

If "Outgoing NAT IP" is configured in the tunnel's environment settings, this IP will be used for masquerading instead. Please make sure it is empty if you want to use TBP.
[[File:Tbp-outgoing-nat-ip.png|thumb|The server's Outgoing NAT IP field needs to be empty for TBP to work]]
[[File:Tbp-server-routes.png|thumb|These are the server routers, here you enter your public IPs]]

{{Colored_box|Text=Please note that the smallest public IP network you can route is a /31 (2 usable IP addresses)!}}

=== Known issues ===

* When a daemon on the server is listening on 0.0.0.0 (any IP), this will take precedence over incoming connections targetting a target in your subnet. saneserver's current default configuration is doing exactly that.

Transparent Bonding Proxy

2026-03-12T07:38:36Z

Christian:

[[Category:General]]
== Transparent Bonding Proxy ==
Transparent Bonding Proxy (TBP) as a '''work in progress''' extension that allows Bonding Proxy to establlish connections using the client's original IP. Without TBP, connections utilizing Bonding Proxy will always use the server's default IP address, even if subnets are properly routed to a client.

=== Prerequisites ===
TBP only works with server routes and masquerading disabled on the client.
[[File:Tbp-prerequisites-1.png|thumb|Where to find the masquerading option in a Teltonika router]]
[[File:Tbp-prerequisites-2.png|thumb|Masquerading turned off]]

SANE server uses IP_TRANSPARENT to bind to non-local IP addresses, which required CAP_ADMIN capabilities. For proper operation, we must identify traffic that matches our Bonding Proxy connections:
# iptables -t mangle -N DIVERT
# iptables -t mangle -A PREROUTING -p tcp -m socket -j DIVERT
# iptables -t mangle -A DIVERT -j MARK --set-mark 1
# iptables -t mangle -A DIVERT -j ACCEPT
Then, create a routing table that defines your routed subnet(s) as local
# ip rule add fwmark 1 lookup 100
# ip route add local 0.0.0.0/0 dev lo table 100
0.0.0.0/0 allows any IP to be used. While this also works, it has security implications - add your routed subnets instead to minimize risks.

Currently, TBP will be activated for any proxy connection initiated by a client with a routed IP.

If "Outgoing NAT IP" is configured in the tunnel's environment settings, this IP will be used for masquerading instead. Please make sure it is empty if you want to use TBP.
[[File:Tbp-outgoing-nat-ip.png|thumb|The server's Outgoing NAT IP field needs to be empty for TBP to work]]
[[File:Tbp-server-routes.png|thumb|These are the server routers, here you enter your public IPs]]

{{Colored_box|Text=Please note that the smallest public IP network you can route is a /31 (2 usable IP addresses)!}}

=== Known issues ===

* When a daemon on the server is listening on 0.0.0.0 (any IP), this will take precedence over incoming connections targetting a target in your subnet. saneserver's current default configuration is doing exactly that.

Downloads

2025-12-16T13:32:00Z

Christian:

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

|}

Main Page

2025-12-08T10:49:50Z

Christian: /* Client and Server */

{{DISPLAYTITLE:Start}}

== Welcome! ==

This is the Bondix Wiki, our ever-growing knowledge base. Here, we collect all things Bondix and former Bondix S.A.NE. 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 S.A.NE 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]

DMZ and 1:1 NAT configuration

2025-12-08T10:46:14Z

Christian:

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

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

== Assumptions ==

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

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

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

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

1. Log in to the Bondix server GUI.

2. Create a **new environment**.

[[File:Addenv1.png|left|frameless|825x825px]]

3. In this environment, set:

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

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

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

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

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

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

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

Replace:

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

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

In the firewall of the Bondix client router:

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

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

Set protocol to all as needed for your use case.

Example screenshot from Teltonika:

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

== Step 5: Make iptables rules persistent ==

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

To ensure the rules are always applied:

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

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

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

On the Bondix server:

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

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

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

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

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

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

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

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

With these settings:

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

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

DMZ and 1:1 NAT configuration

2025-12-08T10:37:32Z

Christian: Created page with "= DMZ and 1:1 NAT configuration with additional static, public IPv4 addresses on the Bondix server = This page describes how to forward traffic from a public IP on the Bondix server to a LAN host behind an Bondix client router using iptables and port forwarding. == Assumptions == * You are operating an own Bondix server with the option to get additional public IPv4 addresses. * You have an additional IP address on the Bondix server (example: ''14.15.16.1''). * The LAN..."

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

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

== Assumptions ==

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

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

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

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

1. Log in to the Bondix server GUI.
2. Create a **new environment**.

[[File:Addenv1.png|frameless]]

3. In this environment, set:

*'''Outgoing NAT IP''' = ''14.15.16.1''

[[File:Add nat ip.png|frameless]]

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

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

[[File:Stats.png|frameless]]

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

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

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

Replace:

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

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

In the firewall of the Bondix client router:

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

* From zone: **Bondix**
* To IP: **192.168.1.2** (LAN client)

Adjust ports and protocols as needed for your use case.

Example screenshot from Teltonika:

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

== Step 5: Make iptables rules persistent ==

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

To ensure the rules are always applied:

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

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

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

On the Bondix server:

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

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

[[File:Fixedip.png|frameless]]

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

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

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

<syntaxhighlight lang="bash">
iptables -A PREROUTING -t nat -d 14.15.16.1 -j DNAT --to 169.254.19.4
iptables -A FORWARD -d 169.254.19.4 -j ACCEPT
</syntaxhighlight>

With these settings:

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

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

File:Fixedip.png

2025-12-08T10:36:48Z

Christian:

fixed ip

File:Dmz teltonika.png

2025-12-08T10:34:55Z

Christian:

dmz teltonika

File:Stats.png

2025-12-08T10:13:14Z

Christian:

stats

File:Add nat ip.png

2025-12-08T10:11:41Z

Christian:

add nat ip

File:Inip.png

2025-12-08T10:06:21Z

Christian:

insert ip

File:Addenv1.png

2025-12-08T10:03:11Z

Christian:

addenv

File:Addenv.png

2025-12-08T10:01:21Z

Christian:

add envirinment

Server Certificates with LetsEncrypt

2025-12-01T09:03:41Z

Christian:

[[Category:Server]]
[[Category:SSL]]
== Set up Bondix SANE 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 S.A.NE 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.)'''

Downloads

2025-11-10T10:06:29Z

Christian:

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

|}

File:Tbp-server-routes.png

2025-09-26T13:08:41Z

Christian: Christian uploaded a new version of File:Tbp-server-routes.png

transparent bonding proxy server routes

Server Capacity

2025-08-21T09:09:36Z

Christian:

[[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 S.A.NE needs 200 MB of RAM per environment on the S.A.NE 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 S.A.NE 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.

Howto essential

2025-08-01T14:40:03Z

Christian: /* And that´s it: */

=== How to start with the Bondix essential cloud service. ===

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

[[Downloads#Teltonika Routers]]

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

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

'''- IMPORTANT!:'''

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

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

'''-'''

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

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

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

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

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

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

Howto essential

2025-08-01T12:20:52Z

Christian:

=== How to start with the Bondix essential cloud service. ===

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

[[Downloads#Teltonika Routers]]

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

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

'''- IMPORTANT!:'''

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

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

'''-'''

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

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

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

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

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

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

Howto essential

2025-08-01T12:19:47Z

Christian:

=== How to start with the Bondix essential cloud service. ===

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

[[Downloads#Teltonika Routers]]

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

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

'''- IMPORTANT!:'''

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

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

'''-'''

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

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

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

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

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

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

File:Bgbf65.png

2025-08-01T12:16:29Z

Christian:

bgbf65

File:Mh65.png

2025-08-01T12:15:22Z

Christian:

mh65

File:Gk65.png

2025-08-01T12:14:26Z

Christian:

gk65

File:Dd53.png

2025-08-01T12:13:27Z

Christian:

dd53

File:Ccf.png

2025-08-01T12:12:42Z

Christian:

ccf

File:Gra44.png

2025-08-01T12:11:37Z

Christian:

gra44

File:Grafik11.png

2025-08-01T12:09:36Z

Christian:

Howto essential

2025-08-01T12:06:46Z

Christian: Created page with "=== How to start with the Bondix essential cloud service. === ==== Installing the Bondix client ==== You can find the latest Bondix client for your Teltonika device on our website at: Downloads#Teltonika Routers 571x571px Please download the client which matches your device and RutOS version. - IMPORTANT!: Please note that the Bondix client is only working with its specific RutOS Version. For example, if you run a Telton..."

=== How to start with the Bondix essential cloud service. ===

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

[[Downloads#Teltonika Routers]]
[[File:Telclient.png|center|frameless|571x571px]]

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

-

IMPORTANT!:

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

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

-

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

and confirm the installation:

[[File:Confirmbondix.png|center|frameless|514x514px]]

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

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

To configure this server, just use the Network DNS menu of your Teltonika device to add DNS servers of your choice (in our example, Google DNS).
[[File:Dnsbondix.png|center|frameless|508x508px]]

==== Setting up the Bondix tunnel ====
After the successful subscription to the '''Bondix Essential Cloud''' service, you will receive an email with your Bondix tunnel credentials. For a speedy start, the most relevant information in the email is your unique '''Bondix QuickConnect code'''.
[[File:Welcomemail.png|center|frameless|424x424px]]
To start, just copy this code from your email and enter it in the '''QuickConnect code''' menu of your Teltonika’s Bondix client:
[[File:Qcc.png|center|frameless|778x778px]]

then switch the Enabled button to active and press the Save configuration button.

And that´s it:
[[File:Finished.png|center|frameless|736x736px]]

File:Finished.png

2025-08-01T12:05:45Z

Christian:

tunnel is up

File:Qcc.png

2025-08-01T12:04:49Z

Christian:

quickconnect code

File:Welcomemail.png

2025-08-01T12:03:36Z

Christian:

Bondix welcome mail

File:Dnsbondix.png

2025-08-01T12:01:24Z

Christian:

dns settings for bondix client

File:Confirmbondix.png

2025-08-01T11:56:59Z

Christian:

confirm dialog

File:Bondixinstallerteltonika.png

2025-08-01T11:54:50Z

Christian:

packagemanager

File:Telclient.png

2025-08-01T11:50:15Z

Christian:

Bondix client Teltonika

Certificates

2025-07-29T13:44:33Z

Christian:

[[Category:Server]]

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

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

== Prerequisites ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Certificates

2025-07-29T13:41:50Z

Christian:

[[Category:Server]]

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

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

== Prerequisites ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Certificates

2025-07-29T13:31:00Z

Christian:

[[Category:Server]]

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

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

== Prerequisites ==

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

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

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

=== Enabling Certificate based tunnels on server ===
To enable the use of certificates for tunnel authentication on a Bondix server, the configuration file /etc/bondixserver.json must be edited.

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

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

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

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

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

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

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

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

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

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

Server

2025-06-04T13:16:12Z

Christian: /* Installing the Linux VM (Ubuntu 20.4) */

[[Category:Server]]
[[Category:Manual]]
[[Main_Page|Start]] > [[Main_Page#Marketing_Material|Marketing Material]] > [[Manuals|Manuals]] > [[Manuals/Sane-server-v01|S.A.NE 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>S.A.NE 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 S.A.NE 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]

Manuals/Server

2025-06-04T13:10:52Z

Christian: /* Installing the Linux VM (Ubuntu 20.4) */

== 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 S.A.NE 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 S.A.NE providing multi-tenancy support. This feature prevents routers assigned to a Tunnel Environment from communicating with each other. If you deactivate “Disable traffic among routers”, routers in the same environment can interact. You can adjust this setting separately for each environment.

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

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

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

Main Page

2025-05-12T12:04:47Z

Christian: /* Client and Server */

{{DISPLAYTITLE:Start}}

== Welcome! ==

This is the Bondix Wiki, our ever-growing knowledge base. Here, we collect all things Bondix and former Bondix S.A.NE. 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.
# <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.

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 were last updated June 2023, so screenshots may vary from the version you can download today. 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]

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

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

Teltonika Portforwarding

2025-05-12T12:02:27Z

Christian:

[[Category:Client]]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

File:Portforward1.png

2025-05-12T11:51:44Z

Christian:

forwarding on Bondix server

Manuals/Server

2025-04-04T09:06:59Z

Christian: remove or replace SANE

== 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) ===
⚠️ '''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 S.A.NE 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 S.A.NE 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>

Manuals/Server

2025-04-04T09:02:31Z

Christian: remove or replace SANE

== 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) ===
⚠️ '''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 S.A.NE 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 S.A.NE Server ==
=== Licensing ===
If your server is not already licensed, you first need to activate the S.A.NE 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 S.A.NE 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 S.A.NE Tunnels ====
To connect a S.A.NE-compatible router to a S.A.NE 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 S.A.NE 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 S.A.NE server. =====
Make sure that the latest Bondix S.A.NE client is installed on your router. Go to the settings menu of your router’s S.A.NE 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 S.A.NE 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 S.A.NE. 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 S.A.NE web monitor for diagnostic purposes.
|-
| 4 Delete Tunnel || Deletes a tunnel permanently without the possibility to restore it.
|}

===== Tunnel Environments =====
In Bondix S.A.NE, 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 S.A.NE 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 S.A.NE 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 S.A.NE 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>

File:3-login.png

2025-04-04T08:06:28Z

Christian: Christian uploaded a new version of File:3-login.png

Server

2025-04-04T07:45:30Z

Christian:

[[Category:Server]]
[[Category:Manual]]
[[Main_Page|Start]] > [[Main_Page#Marketing_Material|Marketing Material]] > [[Manuals|Manuals]] > [[Manuals/Sane-server-v01|S.A.NE 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) ===
⚠️ '''For the installation, you will need root rights.''' ⚠️

Set your firewalls to the following settings:
<nowiki>S.A.NE 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 S.A.NE 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]

Server

2025-04-04T07:44:33Z

Christian: remove or replace SANE

[[Category:Server]]
[[Category:Manual]]
[[Main_Page|Start]] > [[Main_Page#Marketing_Material|Marketing Material]] > [[Manuals|Manuals]] > [[Manuals/Sane-server-v01|S.A.NE 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) ===
⚠️ '''For the installation, you will need root rights.''' ⚠️

Set your firewalls to the following settings:
<nowiki>S.A.NE 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 S.A.NE 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 S.A.NE 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 S.A.NE 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]