<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dataplane on BIFIT Mitigator</title>
    <link>https://docs.mitigator.ru/v26.04/en/tags/dataplane/</link>
    <description>Recent content in Dataplane on BIFIT Mitigator</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://docs.mitigator.ru/v26.04/en/tags/dataplane/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MITIGATOR Installation</title>
      <link>https://docs.mitigator.ru/v26.04/en/install/manual/mitigator/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/install/manual/mitigator/</guid>
      <description>All files are supposed to be placed in the /srv/mitigator working directory:
mkdir -p /srv/mitigator &amp;amp;&amp;amp; \ cd /srv/mitigator 1. Docker Compose Place base Docker Compose configuration in the working directory:
wget https://docs.mitigator.ru/v26.04/dist/docker-compose.yml Download base variable file and save it as .env:
wget https://docs.mitigator.ru/v26.04/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).</description>
    </item>
    <item>
      <title>Core Isolation for Performance Optimization</title>
      <link>https://docs.mitigator.ru/v26.04/en/kb/isolcpus/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/kb/isolcpus/</guid>
      <description>By default, the CPU cores that work with network ports are also used by other subsystems. This can degrade performance and cause Input Errors pps/bps spikes on Port extX/intX graphs. You can take some of the load off these cores by preventing non-critical subsystems from running on them.
To do so:
Specify isolation of the packet processor cores in the core options through the isolcpus=... and rcu_nocbs=... parameters. It is also recommended to add mitigations=off to disable core security patches.</description>
    </item>
    <item>
      <title>Troubleshooting</title>
      <link>https://docs.mitigator.ru/v26.04/en/install/troubleshooting/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/install/troubleshooting/</guid>
      <description>Drivers not loading (modprobe) Symptoms:
When loading a module:
modprobe: FATAL: Module igb_uio not found in directory /lib/modules/4.9.0-6-amd64 When installing a package:
Module build for kernel 4.9.0-6-amd64 was skipped since the kernel headers for this kernel does not seem to be installed. You need to install the linux-headers-amd64 (Debian) package and make sure that the kernel version corresponding to the version of this package is loaded, then run:
dkms autoinstall Docker and docker-compose not working By default, these commands only work for users in the docker group and for root.</description>
    </item>
    <item>
      <title>Packet Processor Settings</title>
      <link>https://docs.mitigator.ru/v26.04/en/kb/dataplane.conf/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/kb/dataplane.conf/</guid>
      <description>The packet processor is configured through the dataplane.conf file.
Put the file into the MITIGATOR working directory and set the required parameters. Other parameters will have the default values.
Comments are specified with #, // or /* */.
Available parameters (with default values):
# Control socket bind address. control_address: 0.0.0.0 # Control socket TCP port. # [1, 65535] control_port: 8888 # Debug control socket TCP port. # [1, 65535] debug_port: 8889 # gRPC control socket TCP port.</description>
    </item>
  </channel>
</rss>