EVE-NG vs Netperf

EVE-NG is a clientless network emulation platform for network, security, and DevOps professionals. It is presented for building virtual proof-of-concept projects, solutions, and training environments for organizations, educators, individuals, and groups. A topology designer supports lab creation, configuration import and export, XML lab files, and picture or map imports. Running nodes can connect through hot links, including to real networks. Listed Professional features include KVM hardware acceleration, Docker and custom Docker support, and up to 1024 nodes per lab. Integrations include RADIUS and Microsoft Active Directory authentication, Docker-integrated Wireshark, and an integrated NAT cloud. Hosting options include Proxmox, VMware platforms, and Google Cloud platform VMs. The free plan allows 7 nodes per instance and 63 per lab, with the Admin role only. EVE-NG Base and RBL are priced on request; RBL supports multiple roles, with added roles priced separately. Community Edition support and end of life ended in June 2026.

Netperf is an open-source, self-hosted utility for measuring network performance. It reports unidirectional throughput and end-to-end latency through a client-server arrangement: netperf runs tests and netserver supplies the server side. Netserver can run as an inetd child or standalone daemon. The manual describes TCP and UDP transfer and request/response tests over IPv4 and IPv6 sockets, plus XTI, DLPI, Unix domain socket, and SCTP tests. Where the platform and build support it, results can include CPU utilization and service demand. Optional configuration enables STREAM pacing, timing histograms, and interim results. The primary distribution is source code, intended for systems without readily available binaries. Reported Windows builds use Cygwin, the Windows DDK, or Microsoft Visual Studio 2003; the README discusses an OSX naming workaround. Hewlett Packard Enterprise released this version under the MIT license. The project warns that its manual may be outdated, and several test families require explicit configuration.