Requirements for installation

To ensure a successful installation of Relay Server, it is necessary to have a Linux operating system based on either Debian or Redhat, with a minimum kernel version of 3.9.0. This requirement guarantees compatibility and optimal performance.

Caution

The Relay Server functionality in an AIR deployment is not automatically available for all users. This feature’s availability is contingent upon specific license configurations.

Users considering the installation and configuration of a Relay Server should liaise with their Binalyze installation advisor as part of the setup process.

Currently, the supported versions for Relay Server are as follows:

• Debian 7 and above
• RHEL (Red Hat Enterprise Linux) 7 and above
• CentOS 7 and above
• Fedora 21 and above
• Ubuntu 14.04 and above
• Pardus 17 and above

Please note that this list may be subject to updates, and you can always refer to the download page and click on “See Supported Versions” for the most up-to-date information on supported systems.

Note

Currently, the recommended system requirements for running Relay Server are 4GB of RAM and 4 CPU cores. However, it’s important to note that these requirements may be subject to change based on the results of a performance test conducted specifically for Relay Server.

Additionally, for Relay Server to function properly, a responder must be installed and registered. The responder acts as the intermediary between the Relay Server and the AIR console, which serves as the management interface for controlling Relay Server’s operations. The seamless interaction between the responder and AIR console facilitates efficient management of the Relay Server’s functionalities.

Note

The Relay Server listens to default SOCKS5 port 1080 and creates connections to the target server (e.g. AIR console). Port 1080 should be available for listening; otherwise, the relay server does not work as expected. As of now, the AIR responder connects to 80 (HTTP), 443 (HTTPS), and 4222 (NATS) ports of the AIR console, so as a result, the Relay Server as a proxy server can connect to the 80, 443, and 4222 ports of the target server. You should keep in mind that any implementation change in the future, like allowing evidence repository connections over the relay server, results in connecting to the appropriate port of the target server.

Note that, the AIR responder will try to connect to port 1080 of the Relay Server to communicate with the AIR console. If the connection cannot be established, the AIR responder falls back to a direct connection to the AIR console.

Danger

As of now, the Relay Server’s default listening port, 1080, cannot be changed and the AIR responders will always try to connect to port 1080 if they are configured to use a relay server.