From Bondix Wiki


Bondix S.A.NE Clients are downward compatible, meaning newer Client builds and/or Server versions may be operated with each other and still function well, but in order to fully benefit from all new features to their full extend though, we recommend you update your Bondix S.A.NE server to the latest version. Please find more information on how to do that at the end of this document.

You can find and download the latest Bondix S.A.NE for your device here: Bondix S.A.NE Releases.


New Backup / Standby Interfaces

On the Bondix S.A.NE Client, interfaces can now be declared as backup: They are listening in at virtually no data usage and will only activate in case the main interface(s) fail. You may set a minimum number of active main interfaces. When the number of active main interfaces falls below this threshold, backup interfaces are activated and used. Please keep the following things in mind when using this feature:

  • Switching to a backup interface will cause a short but probably noticeable delay in data transfer.
  • Backup interfaces will only go back to standby when they are not in use.
  • Backup interfaces may also be activated when a main interface is only performing poorly.

Teltonika FW 07.04.1 Support

We now fully support Teltonika Network’s 07.04.1 firmware. If you intend on switching to this Teltonika firmware release directly from a major earlier version (07.0X.X), we recommend you reset your router before updating to this Bondix Release Version in order to ensure you achieve the bandwidths you’re used to. In this case, don’t forget to backup your settings.



  • Simpler UI: The Client’s settings page was cleaned up so its sorting makes more sense and is easier to understand.
    • Instead of being a part of the presets, the “Encryption” setting has been moved to the “Advanced Settings” tab.
    • For the monitor, the “HTTP Port” and “API Key” entries have been removed in the “Advanced Settings” tab; in the graph itself, the interfaces now again are shown with their names instead of “Channel 1”, “Channel 2”, etc.


  • Layer-3 routing settings: An option to configure routes and server routes directly on the server has been added. Please keep in mind: Server routes are routers that are applied on the server–matching traffic will be routed towards the tunnel. When the client is masquerading (default), no server routes are required. Server routes must be unique across all tunnels and may not overlap.
  • Routing management: Server routes can now be added/removed via bxutil.



  • Layer-2 connection issue: We’ve identified and fixed an issue where a Layer-2 tunnel would not connect.
  • Involuntary restart: We’ve fixed an issue that caused the Client to occasionally restart shortly after disabling the Bondix S.A.NE service.


  • Web interface time-out: We’ve fixed an issue that caused a user to automatically log-out from the Server’s web interface after 10 minutes, regardless of activity.

Download release notes as PDF

April 2023