Data Plane Server Plugins
Plugins that support two-arm operation, where you select Client or Server when adding the plugin from the catalog, are listed below. The server side runs on a Peresvet ST agent and responds to traffic from the client plugin or receives a measurement flow.
Table 190 — Plugins with a server side
| Plugin | Is a server required? | Server-side behavior |
|---|---|---|
| HTTP | No | Receives HTTP/HTTPS traffic and responds according to the configured settings |
| File Transfer (HTTP) | Yes | Sends and receives files over HTTP |
| Malware File Transfer (HTTP) | Yes | Participates in the transfer of PTI files |
| RoCEv2 (beta) | Yes | Receives the RoCEv2 flow |
| Elephant Flow TCP | Yes | Receives the TCP elephant flow |
| Elephant Flow UDP | Yes | Receives the UDP elephant flow |
| L2 Convergence Measurement (UDP) | Yes | Receives UDP measurement flows |
| Latency Measurement (IP/UDP) | Yes | Returns UDP requests so the client can calculate RTT and jitter |
| Dynamic Applications | Yes | Replays the server half of the PCAP scenario |
| PCAP Replay | Yes for stateful mode | Responding side of the replay |
| Network Vulnerabilities (CVE) | Yes | Responds according to the CVE scenario |
| Fuzzing (L3–L7) | No | Provides TCP Flow / UDP Flow on the server |
| Compromised Host | Yes | Emulates a C2 controller |
Two-arm rules:
- The client and server must use matching networks, ports, and certificates when TLS is enabled.
- If no server is added and the target points to an external DUT, the task runs one-arm against the real service. If the target is another agent's network and no server plugin is configured, the connection cannot be established.
- Enable only flow modules on a Fuzzing server; the client generates malformed packets.
- Check the client → server arrow direction in the task diagram.
The following sections describe the server-side configuration for each plugin. For most plugins, the common groups — Receiver, IP header (L3), TCP header (L4), TLS settings, Session settings, and Duration — match the HTTP server plugin (Tables 191–197). Plugin-specific fields are documented separately.