Files
irtt-rs/crates/irtt-server
renovate Bot 72159f55c9
Rust CI / cargo fmt (pull_request) Successful in 18s
Rust CI / cargo check (x86_64-unknown-linux-gnu) (pull_request) Successful in 35s
Rust CI / cargo clippy (pull_request) Successful in 36s
Rust CI / cargo check (x86_64-unknown-linux-musl) (pull_request) Failing after 9s
Rust CI / cargo test (x86_64-unknown-linux-gnu) (pull_request) Successful in 53s
Rust CI / cargo test (x86_64-unknown-linux-musl) (pull_request) Failing after 9s
Rust CI / cargo doc (pull_request) Successful in 26s
Supply chain / cargo-deny advisories (pull_request) Successful in 12s
Supply chain / cargo-deny bans licenses sources (pull_request) Successful in 8s
Fuzz Smoke / cargo fuzz smoke (pull_request) Failing after 30s
Supply chain / actionlint (pull_request) Successful in 4s
Netem Interop / netem interop (pull_request) Successful in 1m7s
fix(deps): update rust crate thiserror to 2.0.21
2026-09-27 18:08:01 +00: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.