network Configuration File

This file contains the settings required for CAS to communicate with OpenVPN, Terminals, and Users.

These settings are precise - there’s no possible adjustments to “improve” performance. The settings either work - or they don’t - and must be fixed. This guide will help explain what each setting does.

Location: /batm/config/network

Settings:

Every line is critical, and no lines are ignored. Remarks will cause errors (do not add remarks to this file).

public_ip: is the logical network adapter IP exposed to the world (where permitted).

• The admin service (CAS GUI) will be exposed at the assigned IP when unprotected by a VPN.

• The IP must exist before you generate vpn for admins or terminals .

gate_bind_ip: is the IP address the gate service is bound to

• The gate service will be exposed at the assigned IP.

• incoming public_ip:7741/tcp is dnated to this ip

• if the IP is missing during start service, you will be asked by batm_manage script to automatically create new loopback interface with default value (10.3.1.1)

master_bind_ip: is the IP address the master service is bound to

• The master service uses this IP to communicate with Terminals.

• The IP must exist for the master service to successfully start.

• if the IP is missing during start service, you will be asked by batm_manage script to automatically create new loopback interface with default value (10.3.2.1)

admin_bind_ip: is the IP address the admin service is bound to.

• The admin service (CAS GUI) will be exposed at the assigned IP.

• if the IP is missing during start service, you will be asked by batm_manage script to automatically create new loopback interface with default value (10.3.2.2)

Examples:

Location: /batm/config/rw/server_admin.port

Settings:

port.defined:

port.detected:

Example: