Invariant vs iPerf2

Invariant validates network configurations against connectivity and security rules in a cross-vendor digital twin. It builds the model from configuration files, so direct access to routers or switches is not required. Users define policies in YAML and evaluate them against network snapshots, including proposed changes before deployment. Results can report policy violations and failures affecting critical flows. Scheduled network scans can trigger incident alerts with virtual traceroutes and virtual route-table differences. The service lists Cisco, Juniper, Palo Alto, and AWS among supported vendors, and integrations including Jenkins, GitHub Actions, LibreNMS, Netmiko, Aerleon, Capirca, IPAM, and SIEM workflows. A CLI, SDK, and API support automation. Listed protocols include BGP, OSPF, IPSec, NAT, policy-based routing, VPN, ACL, and VLAN. Invariant offers hybrid deployment and web/API access. The Basic account is free, billed as a free Basic account with effectively no usage limits. Higher tiers add SSO, larger device counts, and preview features.

iPerf2 measures network traffic performance, including throughput, latency, link capacity, and responsiveness. Testing uses a client to send traffic to a server. It can generate TCP and UDP traffic in one-way, bidirectional, full-duplex, and simultaneous multi-stream configurations. Measurements include one-way delay, round-trip time, jitter, packet loss, and throughput. It supports IPv4, IPv6, and multicast, including source-specific multicast joins, and reports can include enhanced metrics or use CSV format. The project manual describes an Android client with live meters for throughput, latency, and congestion signals. The manual also describes permit-key HMAC authentication using a timestamped HMAC-SHA256 value, with replay limited by a configurable time window. Its Professional feature set includes server access gating and remotely enabled server-side latency histograms. Measurements happen at socket-level reads and writes, so lower-level protocol-header overhead is excluded. iPerf2 and iPerf3 are separate implementations and do not interoperate. It runs on Android, Linux, macOS, and Windows, and can be self-hosted. Both listed editions are free.