Files
irtt-rs/crates/irtt-server
Nils Andreas Svee b36842ee98
Rust CI / cargo fmt (push) Successful in 13s
Rust CI / cargo clippy (push) Successful in 26s
Rust CI / cargo check (x86_64-unknown-linux-musl) (push) Failing after 12s
Rust CI / cargo check (x86_64-unknown-linux-gnu) (push) Successful in 25s
Rust CI / cargo test (x86_64-unknown-linux-gnu) (push) Successful in 44s
Rust CI / cargo test (x86_64-unknown-linux-musl) (push) Failing after 9s
Rust CI / cargo doc (push) Successful in 26s
Fuzz Smoke / cargo fuzz smoke (push) Failing after 31s
Supply chain / cargo-deny advisories (push) Successful in 7s
Supply chain / cargo-deny bans licenses sources (push) Successful in 6s
Supply chain / actionlint (push) Successful in 3s
Netem Interop / netem interop (push) Successful in 1m2s
Semver / cargo-semver-checks (push) Successful in 54s
chore(release): publish docs for irtt-proto, irtt-server, irtt-stats
Version the remaining public crates independently so their crate-specific READMEs, examples, and API doctests are represented in release history.
2026-09-25 00:32:11 +07:00
..

irtt-server

Reusable, Tokio-native library for running an IRTT-compatible UDP server: open negotiation, the bounded session table, echo processing, per-session rate limiting, idle and max-duration expiry, and reply construction.

Looking for the CLI?

If you just want to run a server from the command line, use the irtt-rs application package instead, which installs the irtt-server binary. This crate is the library that binary is built on.

Structure

  • Server — the one-listener primitive: one UDP socket, one deterministic ServerCore, one sequential receive/reply loop.
  • ServerSet — supervises one or more Servers as a single service: binds them all or none, runs each in its own task, and fans one shutdown out to all of them.

Unlike irtt-client, Tokio is not optional here — this crate is intentionally Tokio-native, with no blocking or alternate-runtime variant.

A wildcard listener (0.0.0.0 / [::]) recovers each request's local destination and replies from it, so a client on a second local address is answered from the address it actually contacted. That path is implemented for Linux, macOS, and FreeBSD; a wildcard bind is refused at construction on other targets rather than served incorrectly. Explicit-address listeners are unaffected everywhere.

See examples/ in the repository for runnable examples.

Documentation

Full API documentation is on docs.rs/irtt-server.

Project

Part of irtt-rs, an independent Rust implementation of an IRTT-compatible protocol stack.