fireperf (0.3.0-1) unstable; urgency=medium

  * fireperf uses io_uring where the kernel has it, and sends without
    copying, and falls back to epoll everywhere else
  * A live view in the terminal with a graph of the traffic and every
    client, which works on dark and light terminals
  * Connections can be opened at a fixed rate (--rate), and the client
    tells why connections have failed and how long the handshakes took
  * Requests and responses on every connection (--exchange), resets
    (--reset), and connections that are kept open (--keepalive) and
    checked whether they still work
  * Connections can come from more than one address (--bind), and go to
    names, IPv4 and IPv6 (-4, -6)
  * fireperf speaks the protocols of iperf3 and iperf
  * Machine-readable output with --json
  * Translations, starting with German
  * A man page that explains how fireperf works (fireperf-design(7))

 -- Michael Tremer <michael.tremer@ipfire.org>  Fri, 16 Oct 2026 10:12:51 +0000

fireperf (0.2.0-1) unstable; urgency=medium

  * The direction of data travel has been changed by default to server to
    client
  * With --duplex, the client can now send data, too
  * The statistics output has been extended to show incoming and outgoing
    traffic

 -- Michael Tremer <michael.tremer@ipfire.org>  Tue, 23 Feb 2021 16:02:02 +0100

fireperf (0.1.0-1) unstable; urgency=medium

  * Initial release.

 -- Michael Tremer <michael.tremer@ipfire.org>  Wed, 03 Feb 2021 19:35:23 +0100
