In this section
•List of Supported Operating System Versions
•Additional Packages and Components
•Compatibility with Security Subsystems
You can use Dr.Web Gateway Security Suite on a computer that meets the following requirements:
Parameter |
Requirements |
|---|---|
Platform |
Processors of the following architectures and command systems are supported: •Intel/AMD: 32-bit (IA-32, x86); 64-bit (x86-64, x64, amd64) •ARM64 •E2K (Elbrus) •IBM POWER9, Power10 (ppc64el) |
RAM |
At least 500 MB of free RAM (1 GB or more is recommended) |
Free disk space |
At least 2 GB of free disk space on a volume where the product directories are located |
Operating system |
GNU/Linux (based on kernel version 2.6.37 or later, using glibc library 2.13 or later, systemd initialization system ver. 209 or later), FreeBSD. The supported operating system versions are listed below. The operating system must support the PAM authentication mechanism |
Other |
The following valid network connections: •valid Internet connection to enable updates for virus databases and Dr.Web components; •when operating in the centralized protection mode, connection to the server on the local network is enough; connection to the Internet is not required |
|
To enable the correct operation of the Dr.Web Firewall for Linux component, the OS kernel must be built with the following options: •CONFIG_NETLINK_DIAG, CONFIG_INET_TCP_DIAG; •CONFIG_NF_CONNTRACK_IPV4, CONFIG_NF_CONNTRACK_IPV6, •CONFIG_NETFILTER_NETLINK_QUEUE, The set of required options from the specified list can depend on the relevant OS version. |
To enable the correct operation of Dr.Web Gateway Security Suite, open the following ports:
Purpose |
Direction |
Port numbers |
|---|---|---|
To receive updates |
outgoing |
80 |
To connect to the Dr.Web Cloud service |
outgoing |
2075 (including those for UDP), |
List of Supported Operating System Versions
•GNU/Linux
Platform |
Supported GNU/Linux versions |
|---|---|
x86_64 |
•ALT 8 SP •ALT Server 9, 10 •ALT Workstation 9, 10 •Astra Linux Common Edition (Orel) 2.12 •Astra Linux Special Edition 1.6 (with cumulative patch 20200722SE16), 1.7, 1.8 •CentOS 7, 8 •Debian 9, 10, 11, 12 •Fedora 37, 38 •GosLinux IC6 •Red Hat Enterprise Linux 7, 8 •RED OS 7.2 MUROM, RED OS 7.3 MUROM, RED OS 8 •SUSE Linux Enterprise Server 12 SP3 •Ubuntu 18.04, 20.04, 22.04, 24.04 |
x86 |
•ALT 8 SP •ALT Workstation 9, 10 •CentOS 7 •Debian 10 |
ARM64 |
•ALT 8 SP •ALT Server 9, 10 •ALT Workstation 9, 10 •Astra Linux Special Edition (Novorossiysk) 4.7 •CentOS 7, 8 •Debian 11, 12 •Ubuntu 18.04 |
E2K |
•ALT 8 SP •ALT Server 10 •ALT Workstation 10 •Astra Linux Special Edition (Leningrad) 8.1 (with cumulative patch 8.120200429SE81) •Elbrus-D MCST 1.4 •GS CS Elbrus 8.32 TVGI.00311-28 |
ppc64el |
•CentOS 8 •Ubuntu 20.04 |
|
In ALT 8 SP, Elbrus-D MCST 1.4 and GosLinux IC6 mandatory access control is not supported. |
For other GNU/Linux versions that meet the abovementioned requirements, full compatibility with Dr.Web Gateway Security Suite is not guaranteed. If a compatibility issue occurs, contact our technical support.
•FreeBSD
Platform |
Supported FreeBSD versions |
|---|---|
x86 |
11, 12, 13 |
x86_64 |
11, 12, 13 |
|
Dr.Web Gateway Security Suite can be installed on FreeBSD only from the universal package.
The correct operation of Dr.Web Gateway Security Suite on FreeBSD 13 requires that the compat12x Support Pack is installed. |
Additional Packages and Components
Dr.Web Gateway Security Suite does not require installation of additional packages and OS components (except for the protected server software, see below).
|
For convenient work with Dr.Web Gateway Security Suite from the command line, it is recommended to enable command auto-completion in your command shell (if disabled).
If you encounter any issue with installation of additional packages and components, refer to the documentation of your operating system version. |
•SpIDer Gate can have conflicts with other firewalls installed in your operating system (such as Shorewall and SuseFirewall2 in SUSE Linux Enterprise Server and FirewallD in Fedora, CentOS, Red Hat Enterprise Linux). The conflict manifests itself in the SpIDer Gate error message with code x109 or the Dr.Web Firewall for Linux error message with code x102. Methods to resolve the conflict are described in the section Appendix F. Known Errors, see errors x109 and x102.
•If the OS includes NetFilter earlier than 1.4.15, SpIDer Gate can operate incorrectly. This issue is related to the internal error of NetFilter, and looks like as follows: after disabling SpIDer Gate, the network becomes unstable. If you encounter this issue, it is recommended that you upgrade your OS to a version that includes NetFilter 1.4.15 or later. The ways to resolve this issue are described in the Appendix F. Known Errors section.
For integration with an HTTP proxy server, the installed and configured HTTP proxy server with Squid 3.0 and later is required. Squid must be built with the support of ICAP (compiled with the --enable-icap-client option).
In the mode of an internet barrier and a transparent proxy, there are no requirements for web servers and HTTP proxy servers.
|
Internet barrier and transparent proxy modes can be used only on GNU/Linux. |
Compatibility with Security Subsystems
By default, Dr.Web Gateway Security Suite does not support the SELinux security subsystem. Moreover, Dr.Web Gateway Security Suite operates by default in a reduced functionality mode on the GNU/Linux systems that use mandatory access models (for example, on the systems distributed with the PARSEC mandatory access subsystem, which assigns different privilege levels, so-called mandatory levels, to users and files).
In case of installing Dr.Web Gateway Security Suite on systems with SELinux (as well as on systems that use mandatory access models), it is necessary to additionally configure the security subsystem, so that Dr.Web Gateway Security Suite would operate in a full functionality mode. For details, refer to the Configuring Security Subsystems section.