G4. Proxy Server Configuration File

The drwcsd-proxy.xml configuration file of the Proxy server is presented in the XML format and located in:

For Windows OS: Proxy server installation folder.

For UNIX system-based OS: etc subfolder of the Proxy server installation folder or in the current user's work directory.

The <cache-root /> element

The <drwcsd-proxy /> root element may contain non-obligatory <cache-root /> element which defines the path to the cache directory of the Proxy server. If <cache-root /> element has not been specified, caching data will be saved in the temporary directory of OS user.

The <listen /> element

The <drwcsd-proxy /> root element contains one or several obligatory <listen /> elements which define basic settings of the Proxy Server for receiving connections. A <listen /> element contains one obligatory attribute spec, attributes of which define an interface to "listen" incoming client connections and whether the discovery mode is enabled on this interface. The spec attribute contains following properties:

protocol - type of the protocol for receiving incoming connections. Address which the Proxy server listens is set as an attribute.

port - port which the Proxy server listens.

imitation mode - the mode of Server imitation. Allows detection of the Proxy server as Enterprise Server by the Network scanner.

multicast - multicast group where the Proxy server is located.

Properties values of the spec attribute and their parameters are specified in the table below.

Properties of the spec element

Property

Obliga­tory

Possible values

Parameters of possible values

Allowed

Default

protocol

yes

ip,

ipx,

netbios

 

0.0.0.0

-

-

port

no

port

 

2193

imitation mode

no

discovery

yes, no

no

multicast

no

multicast

 

231.0.0.1

The spec attribute contains one obligatory protocol property and three non-obligatory properties, which are: port, imitation mode and multicast. Depending on value of the protocol property, the list of non-obligatory properties in the spec attribute may vary.

The table below contains the list of non-obligatory properties, which can be set (+) or can not be set (-) in the spec attribute, depending on value of the protocol parameter.

Presence of non-obligatory properties in dependence of the value of protocol parameter

Protocol

Attribute presence

port

discovery

multicast

ip

+

+

+

ipx

+

+

netbios

+

+

The <forward /> element

Redirection of incoming connections is adjusted via the <forward /> element which is a child element of <listen />. The <forward /> element contains one or more obligatory to attributes whose values define addresses of Enterprise Servers where the connection should be redirected to. An address of Enterprise Server is specified according to the The Specification of Network Addresses, in particular, in the following format: tcp/<DNS_name>:<port>.

The <forward /> element is obligatory. Each <listen /> element can contain several <forward /> elements.

The forwarding algorithm for the list of  Enterprise Servers

1.Proxy server loads to RAM the list of Enterprise Servers from the drwcsd-proxy.xml configuration file.

2.The Enterprise Agent connects to the Proxy server.

3.Proxy server forwards the Enterprise Agent to the first Server from the Enterprise Servers list loaded in the RAM.

4.Proxy server rotate the list in the RAM and moves the Enterprise Server from the first position to the end of list.

 

Proxy Server does not save changed order of Servers to its configuration file. After restart of Proxy server, the list of Enterprise Servers is loaded to the RAM in original version, which is stored in the configuration file.

 

5.When the next Agent connects to the Proxy server, procedure is repeated from the step 2.

6.If the Enterprise Server disconnects from the antivirus network (e.g., gets offline or denies of service), the Agent connects to the Proxy server repeatedly and procedure is repeated from the step 2.

Example of drwcsd-proxy.xml configuration file

<?xml version="1.0"?>

<drwcsd-proxy>

<!-- Specify path to cahe directory, if not specified will create directory in user temp -->

<cache-root>C:\Work\es_head\build\a-x86\bin\var</cache-root>

 

<!-- property: ip, ipx, netbios, unx: define protocol family and address of addapter -->

<!-- property: port: define port to listen on. Default 2193 or 23 for netbios -->

<!-- property: name: define discovery name. Default drwcs -->

<!-- property: discovery: define should proxy run discovery server too -->

<!-- property: multicast: define should proxy enter to multicast group -->

<!-- For example -->

<!-- Listen on IN_ADDR_ANY port 2193, run discovery on 231.0.0.1 -->

<listen spec="ip(), multicast()">

  <!-- one or more forward tags-->

  <forward to="tcp/server1.isp.net:2193"/>

  <forward to="tcp/server2.isp.net:2193"/>

</listen>

 

<!-- Listen on ipv6 IN6_ADDR_ANY, port 2194, run discovery on ff18::231.0.0.1 -->

<listen spec="ip([]), port(2194), multicast()">

  <forward to="tcp/server1.isp.net:2193"/>

  <forward to="tcp/server2.isp.net:2193"/>

</listen>

 

<!-- Listen on default ipx, port 2194, run simple discovery -->

<listen spec="ipx(), discovery()">

  <forward to="tcp/server1.isp.net:2193"/>

  <forward to="tcp/server2.isp.net:2193"/>

</listen>

<!-- Listen on default netbios, port 23, lana 0, run simple discovery -->

<listen spec="netbios(), discovery()">

  <forward to="tcp/server1.isp.net:2193"/>

  <forward to="tcp/server2.isp.net:2193"/>

</listen>

</drwcsd-proxy>