https://docs.mitigator.ru/v26.08/en/install/manual/ Manual setup For experienced administrators, non-standard cases and those who want to figure it out. System preparation It is necessary to provide: a suitable network card driver; allocation of huge memory pages (hugepages); Docker and Docker Compose. MITIGATOR Setup and launch Place compose file and set global system parameters. Configure the use of network ports and CPU cores by the packet processor. Automate the binding of drivers to network ports and the launch of MITIGATOR. Download MITIGATOR Docker images. Hugo en https://docs.mitigator.ru/v26.08/en/install/manual/system/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.08/en/install/manual/system/ Hardware Platform Supports work on AMD and Intel platforms with x86-64 architecture. AMD platforms require BIOS setup for optimal performance. Hyper-threading It is recommended to enable hyper-threading (HT) in the BIOS. https://docs.mitigator.ru/v26.08/en/install/manual/mitigator/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.mitigator.ru/v26.08/en/install/manual/mitigator/ All files are supposed to be placed in the /srv/mitigator working directory: mkdir -p /srv/mitigator && \ cd /srv/mitigator 1. Docker Compose Place base Docker Compose configuration in the working directory: wget https://docs.mitigator.ru/v26.08/dist/docker-compose.yml Download base variable file and save it as .env: wget https://docs.mitigator.ru/v26.08/dist/env -O /srv/mitigator/.env In the .env file, specify: System version (VERSION). The microarchitecture of the processor from the list specified in the (ARCH) example file. The maximum number of IPv4 protection policies (DATA_PLANE_NR_POLICIES). The maximum number of IPv6 protection policies (DATA_PLANE_NR_POLICIES_IPV6). Instance name in the cluster (MITIGATOR_OWN_NAME, required). IP address for container-to-host access (MITIGATOR_HOST_ADDRESS, required). IP address or domain name for API and UI clients (MITIGATOR_PUBLIC_ADDRESS, required). Master secret used to encrypt sensitive settings (MITIGATOR_MASTER_SECRET, required). When running in a cluster, master secret must be the same on all MITIGATOR instances. Proxy for the license server (ls.mitigator.ru), mail notifications and the Vestochka service. Time zone (TZ). Token for interaction between the backend and the watchhog (TOKEN). The .env file is set to TOKEN by default. It is required to change it. When running in a cluster, TOKEN must be the same on all MITIGATOR instances. These settings are described in detail inside the example file.