Client: Difference between revisions

From Bondix Wiki
No edit summary
 
(13 intermediate revisions by one other user not shown)
Line 1: Line 1:
The Bondix SANE client is the software that you install on your [[Client/Supported Devices|supported]] router, which establishes a connection to the [[Server|server]] using multiple WAN links.
The Bondix SANE client is the software that you install on your router, which establishes a connection to the [[Server|server]] using multiple WAN links. The software itself is a linux userspace program, but installation packages for different routers are available, that take care of most of the configuration.  


For '''OpenWRT''' based routers, please check [[Client/OpenWRT|this page]].  
This page covers the barebone linux application. Please check out the [[Teltonika]] page for installation & usage on these routers.  


= Installation =
==Configuration==
Log into your router via SSH and do the following:
Configuration is done using [https://www.json.org/ JSON] commands. These can either be sent via a raw TCP socket (localhost:5113), or written to a configuration file (in a json-array) that is parsed on start-up.
{| class="wikitable"
|-
| Create installation directory || <code>mkdir -p /opt/bondix
cd /opt/bondix</code>
|-
| Download installation package || <code>curl -o sane.tar.gz <DOWNLOAD-URL></code>
|-
| Extract package || <code>tar -xvzf sane.tar.gz</code>
|}


You can verify that the correct version has been installed with the command
By default, SANE checks for the existence of a configuration file in its installation directory (e.g. <code>/opt/bondix/client/saneclient.json</code>) and at <code>/etc/saneclient.json</code>. If you want SANE to load a configuration from a different location, you can specify it using a command line parameter.
<code>/opt/bondix/client/saneclient --version</code>


If successful, it should print its version string.
===Quick Start===
 
= Configuration =
Configuration is done using [https://www.json.org/ JSON] commands. These can either be sent via a raw TCP socket (localhost:5113), or written to a configuration file (in a json-array) that is parsed at start-up. This allows both a fixed configuration as well as adjustments during runtime without the need to restart the service. By default, SANE checks for the existence of a configuration file in its installation directory (e.g. <code>/opt/bondix/client/saneclient.json</code>) and at <code>/etc/saneclient.json</code>. If you want SANE to load a configuration from a different location, you can specify it using a command line parameter.
 
== Quick Start ==
This example provides the minimal necessities to get a tunnel up and running:
This example provides the minimal necessities to get a tunnel up and running:
  <nowiki>[
  <nowiki>[
  {"action": "create", "target": "tunnel", "name": "TUNNELNAME", "password": "TUNNELPASSWORD"},
    {"action": "create", "target": "tunnel", "name": "TUNNELNAME", "password": "TUNNELPASSWORD"},
  {"action": "add-server", "target": "tunnel", "host": "ENDPOINTSERVER", "port": "443"},
    {"action": "add-server", "target": "tunnel", "host": "ENDPOINTSERVER", "port": "443"},
  {"action": "create-interfaces", "target": "tunnel", "interfaces": {
    {"action": "create-interfaces", "target": "tunnel", "interfaces": {
    "eth1": "mobileAggressive",
      "eth1": "mobileAggressive",
    "wwan0": "mobileAggressive",
      "wwan0": "mobileAggressive",
    "wwan1": "mobileAggressive"
      "wwan1": "mobileAggressive"
  }},
    }},
  {"target": "tunnel", "action": "set-preset", "preset": "bonding"}
    {"target": "tunnel", "action": "set-preset", "preset": "bonding"}
]
  ]
</nowiki>
  </nowiki>


== Command Structure ==
===Configuration Commands===
A JSON command has the following structure:
For a complete reference list of available commands, see [[Client Configuration]].
<code>{"target": "<module>", "action": "<command>", [...additional values...]}</code>


Where <module> specifies the configuration submodule and <command> specifies what should be done.
===Tunnel Configuration===
Tunnels and channels have many configurable values, that are managed using [[Presets]].  


== System Commands ==
=Running=
{| class="wikitable"
The software can be run in the shell using <code>/opt/bondix/client/saneclient</code>, where it will run in the foreground. However, it is recommended to start the service automatically on startup, which can be different depending on the platform.
|-
|
<nowiki>{"target": "system",
  "action": "shutdown"
}
</nowiki>
||
=== shutdown ===
Shuts down the client and terminates.


|-
===Parameters===
|
<nowiki>{"target": "system",
  "action": "set-log",
  "file": "/var/log/saneclient.log",
  "fileMode": "append"
}
</nowiki>
||
=== set-log ===
Enables logging to file or changes output file.
{| class="wikitable"
{| class="wikitable"
|+ Parameters
|-
|-
| file || The filename that the log should be written to. Required.
|<code>--daemon</code>||Runs the software as a daemon.
|-
|-
| fileMode|| can be <code>append</code> or <code>overwrite</code>.  Required.
|<code>--nopid</code>|| Does not attempt to create a pid-file at <code>/var/run/saneclient.pid</code>
|}
 
|-
|
<nowiki>{"target": "system",
  "action": "set-webinterface",
  "host": "0.0.0.0",
  "port": "80",
  "allowConfig": false,
  "allowMonitor": true,
  "configApiKey": "123456",
  "webroot": "/tmp/"
}
</nowiki>
|| Enables the integrated webserver & debug webinterface.
{| class="wikitable"
|+ Parameters
|-
| host || IP that the service should listen on. Required.
|-
| port || TCP Port that the service should listen on. Required.
|-
|-
| allowConfig || En- or disables web configuration. Not required, enabled by default.
|<code>--listflags</code>||Lists available feature flags
|-
|-
| allowMonitor || En- or disables web monitor. Not required, enabled by default.
|<code>--flags <FLAG1> <FLAG2>... </code>||Enables the specified flag(s). Multiple flags are separated using space.
|-
|-
| configApiKey || The password required to access configuration & monitor. Not required, "123456" by default.
|<code></path/to/filename.json></code>||JSON configuration file that should be used
|-
| webroot || Web root directory. Points to the "www" subdirectory in installation directory. Not required, changing not advised.
|}
|}
|}


== Tunnel Commands ==
===Feature Flags===
{| class="wikitable"
Feature flags are switches that enable certain features that are otherwise unavailable. These features are usually experimental and should be used with caution.
|-
|
<nowiki>{"target": "tunnel",
  "action": "create",
  "name": "MyTunnel",
  "password: "1234",
  "server": "10.0.0.1",
  "interfaceName": "bndx0",
  "values": {...}
}
</nowiki>
||
=== create ===
Sets up basic tunnel configuration.
{| class="wikitable"
|+ Parameters
|-
| name || Tunnel Name. Required.
|-
| password || Password. Required.
|-
| server || Endpoint target IP. Optional.
|-
| interfaceName|| Desired name of the virtual tunnel network interface. Optional.
|-
| values || A JSON object containing configuration parameters for the tunnel.
|}
 
|-
|
<nowiki>{"target": "tunnel",
  "action": "add-server",
  "host": "10.0.0.1",
  "port": "443"
}
</nowiki>
||
=== add-server ===
Adds a endpoint server. If multiple servers are added, the client will cycle through
them until a connection has been established successfully.
{| class="wikitable"
|+ Parameters
|-
| host|| IP or host of the destination server. Required.
|-
| port || Port of the destination server. Optional (Default: "443").
|}
 
|-
|
<nowiki>{"target": "tunnel",
  "action": "create-interfaces",
  "interfaces": {
    "wwan0": "mobile",
    "eth1": "ethernet"
  }
}
</nowiki>
||
=== create-interfaces ===
Creates channels for the specified interfaces using [[Client/Presets|presets]].
{| class="wikitable"
|+ Parameters
|-
| interfaces|| a JSON object where each key is a network interface name, with the corresponding value being a [[Client/Presets|preset]] name. Required.
|}
 
|-
|
<nowiki>{"target": "tunnel",
  "action": "set-preset",
  "preset": "Bonding"
}
</nowiki>
||
=== set-preset ===
Applies a tunnel preset. See [[Client/Presets|Presets]] for more info.
{| class="wikitable"
{| class="wikitable"
|+ Parameters
|-
|-
| name || Name of the tunnel preset. Required.
|useBlake||Switches from SHA256 to the "blake" hashing algorithm.
|}
 
|-
|-
|
|useBlake3||Switches to the "blake3" hashing algorithm.
<nowiki>{"target": "tunnel",
  "action": "set-ifname",
  "name": "bondix0"
  }
}
</nowiki>
||  
=== set-ifname ===
Renames the virtual network tunnel interface.
{| class="wikitable"
|+ Parameters
|-
|-
| name || The name that the interface should be renamed to. Required.
|disableHash||Disables hashing completely
|}
 
|-
|-
|
|useMMSG||uses useMMSG linux socket API to send & receive multiple UDP packets at once.
<nowiki>{"target": "tunnel",
  "action": "set-cert-check",
  "enabled": true
  }
}
</nowiki>
||  
=== set-cert-check ===
Enables or disables verification of the server's SSL certificate. ''TODO: Which root cert dir is used when no custom root certificate is provided?''
{| class="wikitable"
|+ Parameters
|-
|-
| enabled || Enables or disables SSL certificate verification. Required.
|channelRoutes||Makes the client create specific routes for each channel. Experimental, do not use.
|}
 
|-
|-
|
|bondingProxy||<s>Enables the TCP [[Bonding Proxy]]</s>. Now always enabled
<nowiki>{"target": "tunnel",
  "action": "set-root-ca",
  "file": "/etc/ssl/foobar.pub"
  }
}
</nowiki>
||
=== set-root-ca ===
Specifies a root certificate that can be used to verify the authenticity of the remote server. When used, SSL server verification will be automatically enabled.
{| class="wikitable"
|+ Parameters
|-
| file || location of the public root certificate file. Required.
|}
|}


|-
==bndutil==
|
bndutil is a command line utility that allows to query and modify SANE during runtime. It uses the configuration TCP socket
  <nowiki>{"target": "tunnel",
  <nowiki>root@Teltonika-RUTX12:/opt/bondix/client# ./bndutil
   "action": "set-certificate",
   Usage:
   "cert": "/etc/ssl/foobar.pem"
    bndutil [--json] <command>
   "key": "/etc/ssl/foobar.key"
              --json  switch to JSON output
  }
    
}
   Available commands:
</nowiki>
    * bndutil status
||
    * bndutil get
=== set-certificate ===
    * bndutil set <propertyName1> <propertyValue1> [propertyName2] [propertyValue2] ...
Loads a tunnel client certificate. See [[Certificates]] for further information.
    * bndutil get-interface <index>
{| class="wikitable"
    * bndutil set-interface <index> <propertyName1> <propertyValue1> [propertyName2] [propertyValue2] ...
|+ Parameters
    * bndutil shutdown
|-
    * bndutil restart
| cert || location of the public certificate file. Required.
      (tunnel reset & reconnect)
|-
  </nowiki>
| key || location of the private certificate key file. Required.
|}


|-
==speedtest==
|
Speedtest is a small utility that downloads (and discards) data via HTTP(s) using one or more WAN interfaces. It is useful to compare performance of each individual interface and the combined bandwidth over SANE's virtual tunnel interface.
  <nowiki>{"target": "tunnel",
  <nowiki>root@Teltonika-RUTX12:/opt/bondix/client# ./speedtest
  "action": "embed-certs",
   Usage: speedtest [--json] <download-url> <intf1> [intf2] ...</nowiki>
  "cert": "...",
   "key": "...",
  "root": "..."
  }
}
</nowiki>
||
=== embed-certs ===
A helper functions to embed tunnel & root certificate inside the configuration instead of an external file. Performs the same actions as set-certificate and set-root-ca combined.
{| class="wikitable"
|+ Parameters
|-
| cert || The tunnel public certificate as string. Required.
| key|| The tunnel private certificate key as string. Required.
| root || The public root certificate for server verification. Required.


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


 
Testing performance of the tunnel:
|}
<nowiki>./speedtest http://speed.hetzner.de/100MB.bin tun0</nowiki>
 
 
= Running =
The software can be run in the shell using <code>/opt/bondix/client/saneclient</code>, where it will run in the foreground. However, it is recommended to start the service automatically on startup, which can be different depending on the platform.
== Parameters ==
{| class="wikitable"
|-
| <code>--daemon</code> || Runs the software as a daemon.
|-
| <code>--nopid</code> || Does not attempt to create a pid-file at <code>/var/run/saneclient.pid</code>
|-
| <code>--listflags</code> || Lists available feature flags
|-
| <code>--flags <FLAG1> <FLAG2>... </code> || Enables the specified flag(s). Multiple flags are separated using space.
|-
| <code></path/to/filename.json></code> || JSON configuration file that should be used
|}
== Feature Flags ==
Feature flags are switches that enable certain features that are otherwise unavailable. These features are usually experimental and should be used with caution.
{| class="wikitable"
|-
| useBlake || Switches from SHA256 to the "blake" hashing algorithm. Depending on architecture, this can slightly improve performance.
|-
| useBlake3 || Switches to the "blake3" hashing algorithm. Depending on architecture, this can slightly improve performance.
|-
| disableHash || Disables hashing completely, allowing potential MitM, with a vast speed improvement.
|-
| useMMSG || uses useMMSG linux socket API to send & receive multiple UDP packets at once. This improves performance under load, while stable there are some corner cases which can trigger error messages in the log.
|-
| channelRoutes || Makes the client create specific routes for each channel. Experimental, do not use.
|-
| bondingProxy || Enables the TCP [[Bonding Proxy]].
|}

Latest revision as of 11:58, 16 July 2024

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

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

Configuration

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

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

Quick Start

This example provides the minimal necessities to get a tunnel up and running: 

[
    {"action": "create", "target": "tunnel", "name": "TUNNELNAME", "password": "TUNNELPASSWORD"},
    {"action": "add-server", "target": "tunnel", "host": "ENDPOINTSERVER", "port": "443"},
    {"action": "create-interfaces", "target": "tunnel", "interfaces": {
      "eth1": "mobileAggressive",
      "wwan0": "mobileAggressive",
      "wwan1": "mobileAggressive"
    }},
    {"target": "tunnel", "action": "set-preset", "preset": "bonding"}
  ]

Configuration Commands

For a complete reference list of available commands, see Client Configuration.

Tunnel Configuration

Tunnels and channels have many configurable values, that are managed using Presets.

Running

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

Parameters

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

Feature Flags

Feature flags are switches that enable certain features that are otherwise unavailable. These features are usually experimental and should be used with caution.

useBlake Switches from SHA256 to the "blake" hashing algorithm.
useBlake3 Switches to the "blake3" hashing algorithm.
disableHash Disables hashing completely
useMMSG uses useMMSG linux socket API to send & receive multiple UDP packets at once.
channelRoutes Makes the client create specific routes for each channel. Experimental, do not use.
bondingProxy Enables the TCP Bonding Proxy. Now always enabled

bndutil

bndutil is a command line utility that allows to query and modify SANE during runtime. It uses the configuration TCP socket 

root@Teltonika-RUTX12:/opt/bondix/client# ./bndutil
  Usage:
     bndutil [--json] <command>
              --json  switch to JSON output
  
  Available commands:
    * bndutil status
    * bndutil get
    * bndutil set <propertyName1> <propertyValue1> [propertyName2] [propertyValue2] ...
    * bndutil get-interface <index>
    * bndutil set-interface <index> <propertyName1> <propertyValue1> [propertyName2] [propertyValue2] ...
    * bndutil shutdown
    * bndutil restart 
      (tunnel reset & reconnect)

speedtest

Speedtest is a small utility that downloads (and discards) data via HTTP(s) using one or more WAN interfaces. It is useful to compare performance of each individual interface and the combined bandwidth over SANE's virtual tunnel interface. 

root@Teltonika-RUTX12:/opt/bondix/client# ./speedtest
  Usage: speedtest [--json] <download-url> <intf1> [intf2] ...

E.g., to test performance of each WAN interface directly: 

./speedtest http://speed.hetzner.de/100MB.bin wwan0 wwan1 wwan2

Testing performance of the tunnel: 

./speedtest http://speed.hetzner.de/100MB.bin tun0
Retrieved from "https://wiki.bondix.dev/index.php?title=Client&oldid=697"