Remote Configuration of Dr.Web Proxy Server

After connecting Dr.Web Proxy Server to Dr.Web Server, you can configure Dr.Web Proxy Server remotely using the Control Center.

info

Detailed information on connection settings and about quick connection using the command line is given in the Installation Manual, section Connecting Dr.Web Proxy Server to Dr.Web Server.

warning

Dr.Web Proxy Server can accept settings only from a specific set of connected Dr.Web Servers that are marked as managing. If none of the Dr.Web Servers is marked as managing, then the Proxy Server connects to all Dr.Web Servers by rotation until it finds the first valid (not empty) configuration.

If a Dr.Web Server is marked as non-managing (the Managing Dr.Web Server parameter is set to No), Dr.Web Proxy Server cannot receive any settings from it. It also means that later on, this Dr.Web Server cannot be set as managing for the Dr.Web Proxy Server remotely. In this case you need to change the <forward to="" master=""> parameter value in the Dr.Web Proxy Server configuration file manually (see Appendices, F4. Dr.Web Proxy Server Configuration File).

Specifying Dr.Web Proxy Server settings

1.Select the Anti-virus network item in the main menu of the Control Center. In the window that opens, click the name of Dr.Web Proxy Server or the Proxies group and its subgroups in the hierarchical list.

2.Select Dr.Web Proxy Server in the opened control menu. The Settings section opens.

3.On the Certificate tab, you can set the list of Dr.Web Server certificates. You must set all certificates of all Dr.Web Servers to which Dr.Web Proxy Server connects and to which the client traffic is forwarded.

The Dr.Web Server certificate is required to connect to Dr.Web Server for remote configuration of settings and to support the traffic encryption between Dr.Web Server and Dr.Web Proxy Server.

Dr.Web Proxy Server certificate is signed with the Dr.Web Server certificate and private key (the procedure is performed automatically on Dr.Web Server after the connection is established, and does not require any administrator intervention) and is required to connect Dr.Web Agents and to support the traffic encryption between Dr.Web Agents and Dr.Web Proxy Server.

4.On the Listen tab, you can specify the parameters of traffic receiving and forwarding by Dr.Web Proxy Server.

If you are using unified network listening settings, you can specify one set of settings for all client connections, and a different set of settings for each Dr.Web Server.

To add another set of settings, click icon-item-add.

To remove a set of settings, click icon-item-remove next to the set you want to remove.

For each set you can specify the following Dr.Web Proxy Server operation parameters separately:

a)In the listening settings section:

In the Address to listen field, specify an IP address that Dr.Web Proxy Server will "listen" on. Inputting 0.0.0.0 instructs to "listen" on all interfaces.

info

Addresses should be specified in the network address format described in the Appendices, section. Appendix D. The Specification of Network Addresses.

In the Port field, specify the port number on which Dr.Web Proxy Server will listen. By default, it is port 2193.

Set the Discovery flag to enable the Dr.Web Server emulation mode. This mode allows clients to detect Dr.Web Proxy Server as Dr.Web Server during multicast requests.

Set the Multicasting flag so that Dr.Web Proxy Server responds to multicast requests sent to Dr.Web Server.

In the Multicast group field, specify the IP address of a multicast group to which Dr.Web Proxy Server should belong. The specified interface will be listened to by the Proxy Server for interaction with clients during active Dr.Web Servers searches. If you leave this field blank, Dr.Web Proxy Server will not be included in any multicast group. The default multicast group to which Dr.Web Server is included is 231.0.0.1.

b)In the Settings for connection with clients section:

In the Encryption drop-down list, select the encryption mode for data traffic between Dr.Web Proxy Server and the served clients: Dr.Web Agents and Dr.Web Agent installers.

In the Compression drop-down list, select the compression mode for data traffic between Dr.Web Proxy Server and clients: Dr.Web Agents and Dr.Web Agent installers. Select the compression level (from 1 to 9) in the Compression level field.

c)In the Settings for connection with Dr.Web Servers section, you can specify the list of Dr.Web Servers to which the traffic will be forwarded.

The order of Dr.Web Servers in the list defines the order of client traffic redirection and the order of connection of Dr.Web Proxy Server to Dr.Web Servers for receiving the settings. To change the Dr.Web Server order, drag the required lines with the mouse.

To manage Dr.Web Servers, use the buttons on the toolbar of the Dr.Web Server list:

icon-new-edit edit the connection settings for the selected Dr.Web Server.

icon-new-add add the connection settings for the selected Dr.Web Server.

icon-new-delete remove the connection settings for the selected Dr.Web Server.

The window where you can edit and add the connection settings for a Dr.Web Server provides the following options:

In the Managing Dr.Web Server drop-down list, select one of the following options to set the Dr.Web Server in the managing role:
Yes—the managing role is explicitly assigned to Dr.Web Server. You can assign managing roles to any number of Dr.Web Servers; Dr.Web Proxy Server connects to all the managing Dr.Web Servers in the order they are listed in the settings until it gets the first valid (not empty) configuration.
No—the managing role will not be assigned to Dr.Web Server under any circumstances. You can also choose not to assign the managing role to any Dr.Web Servers. In this case, Dr.Web Proxy Server parameters (including the assignment of managing Dr.Web Servers) can be configured only locally via Dr.Web Proxy Server configuration file (see Appendices, F4. Dr.Web Proxy Server Configuration File).
Possible—Dr.Web Server will assume the managing role only if there are no explicit managing Dr.Web Servers (those for which the value of this option is Yes).

In the Redirection address field, specify the address of Dr.Web Server to which the connections established by Dr.Web Proxy Server will be forwarded. It is recommended that you use Dr.Web Server name in the FQDN format as the Dr.Web Server address.

info

If the Redirection address field is not specified or the udp/ value is set, Dr.Web Proxy Server will use the detection service to find Dr.Web Server by sending multicast requests (see step 9).

 

Addresses should be specified in the network address format described in the Appendices, section. Appendix D. The Specification of Network Addresses.

In the Encryption drop-down list, select the encryption mode for data traffic between Dr.Web Proxy Server and the specified Dr.Web Server.

In the Compression drop-down list, select the compression mode for data traffic between Dr.Web Proxy Server and specified Dr.Web Server. Select the compression level (from 1 to 9) in the Compression level field.

In the table, you can specify the traffic limitation settings in the same way as the Dr.Web Server settings given in the Updates and Installations sections.

5.On the Cache tab, specify the following Dr.Web Proxy Server caching settings:

Set the Enable caching flag to cache the data transferred by Dr.Web Proxy Server and specify the following parameters:

In the Revisions deleting interval (min) field, specify the interval at which old revisions should be deleted from the cache if their number exceeds the maximum number of revisions that should remain. The value is set in minutes. The default value is 60 minutes.

In the Number of revisions to remain field, specify the maximum number of each product revisions to remain in the cache after the purge. By default, the last 3 revisions are kept, and the older revisions are deleted.

In the Unload interval of unused files (min) field, specify the time interval in minutes for unloading unused files from the memory. The default value is 10 minutes.

Set the Use proactive caching flag to load new revisions for the selected products from Dr.Web Server to Dr.Web Proxy Server according to the schedule below. During this period, revisions will be loaded to Dr.Web Proxy Server as soon as Dr.Web Server receives them from GUS. If the flag is cleared, new revisions will be downloaded to Dr.Web Proxy Server only when Dr.Web Agent requests them from Dr.Web Server.

In the list below, set the flags for the products you want to synchronize.

In the Repository synchronization timetable section, specify the schedule for loading the updates for the selected products.
To change the type of data transfer limitations, click the corresponding table cell. Also, you can select several time cells using drag and drop.
The color of the cells changes cyclically according to the legend below the table: data transfer can be either allowed without limitations or prohibited.

6.On the Events tab, specify the following parameters of event delivery:

Set the Cache events flag to cache events received from Dr.Web Agents. In this case, the events will be sent to Dr.Web Server every 15 minutes for the period of time specified in the schedule below. If caching is disabled, events will be sent to Dr.Web Server immediately after they are received by Dr.Web Proxy Server.

In the Events sending timetable section, specify the schedule for sending events received from Dr.Web Agents.
To change the type of data transfer limitations, click the corresponding table cell. Also, you can select several time cells using drag and drop.
The color of the cells changes cyclically according to the legend below the table: event transmission can be allowed without limitations or prohibited.

7.On the Dump tab, specify the following settings:

Set the Create memory dumps flag to create memory dumps if critical errors occur in Dr.Web Proxy Server operation.

In the Maximum number of dumps field, specify the maximum number of memory dumps. When the specified value is reached, the oldest dumps are deleted when new dumps are created. Memory dumps setup is available for Windows OS only.

8.On the DNS tab, you can configure the parameters of DNS server usage. The settings are similar to the DNS settings for Dr.Web Server.

9.On the Discovery tab, you can configure the settings for saving responses to multicast requests when searching for Dr.Web Servers for redirecting clients (see step 4c).

For positive responses, sec.—the time (in seconds) for storing the list of Dr.Web Servers that responded to the multicast request during Dr.Web Server look-up. After the specified period of time, the request is sent again.

For negative responses, sec.—the time (in seconds) for storing the information that none of Dr.Web Servers has responded to the multicast request. After the specified period of time, the request is sent again.

10.On the Updates tab, you can configure the parameters of Dr.Web Proxy Server automatic software update from Dr.Web Server:

Set the Enable automatic update flag to download for Dr.Web Server and install new Dr.Web Proxy Server revisions automatically. The update schedule depends on Dr.Web Proxy Server proactive caching settings (see step 5):

a)If Dr.Web Proxy Server is not included in the list for proactive caching (even if caching is not used), then Dr.Web Proxy Server updates will be downloaded and installed according to the automatic update schedule.

b)If Dr.Web Proxy Server is included on the proactive caching list, Dr.Web Proxy Server updates will be automatically downloaded according to the proactive caching schedule. When a new revision of the Proxy Server is received, the update to this revision is performed according to the automatic update schedule.

In the Automatic update schedule section, specify the schedule according to which the automatic updates will be performed.
To change the type of data transfer limitations, click the corresponding table cell. Also, you can select several time cells using drag and drop.
The color of the cells changes cyclically according to the legend below the table: update delivery can be either allowed without traffic limitations or forbidden.

11.On the Log tab, you can select the verbosity level of the Dr.Web Proxy Server log. The following options are available:

Critical error—messages on critical operation errors only;

Error—messages on operation errors;

Warning—warnings on errors;

Notification—important information messages;

Information—information messages;

Trace (0–3)—event tracing with varying detail levels (Trace3 being the most detailed);

Debug (0–3)—debug messages with varying detail levels (Debug3 being the most detailed);

All—all messages (equivalent to Debug3).

12.When you are finished editing, click Save.