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 already exist to successfully install CAS.

• It is the target IP for VPNs for Admins or Terminals.

gate_bind_ip: the Gate service binds to this existing IP interface.

• The Gate service will be exposed at the assigned (internal, protected, private) IP.

• Incoming TCP traffic to the public_ip on port 7741 is forwarded to this interface.

• 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: the Master service is bound to this IP/interface.

• The Master service uses this (internal, protected, private) IP to communicate with Terminals.

• The IP/interface must exist for the Master service to successfully start.

• if the IP is missing during service startup, the batm_manage script will ask to automatically create a new loopback interface with the default value (10.3.2.1).

admin_bind_ip: the Admin service is bound to this IP/interface.

• The Admin service (CAS GUI) will be exposed at the (internal, protected, private) specified IP.

• if the IP is missing during service startup, the batm_manage script will ask to automatically create a new loopback interface with the default value (10.3.2.2)

Examples:

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

Settings:

port.defined:

port.detected:

Example: