Files

T

enricobuehlerandClaude Fable 5 5807d3a8a6 fix(tools): the loss harness catches up with seal_streamed_chunk's slice flag

49bc93cd grew seal_streamed_chunk a slice_end parameter and updated every
caller except this one — the Linux clippy leg has been red since (run
10615+). false = the legacy full-FEC-block granularity the harness always
exercised; its loopback client never advertises the P2 slice wire.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-31 18:16:40 +02:00

src

fix(tools): the loss harness catches up with seal_streamed_chunk's slice flag

2026-07-31 18:16:40 +02:00

Cargo.toml

chore(unsafe): the workspace adopts the drivers' unsafe discipline

2026-07-28 21:31:41 +02:00

README.md

docs: repo-wide housekeeping — sync README & docs with the code as shipped

2026-07-10 09:13:42 +02:00

README.md

loss-harness

A FEC loss-resilience sweep for punktfunk-core. It drives access units through the in-process loopback at increasing packet-loss rates — for both FEC schemes (GF(2⁸) and GF(2¹⁶)) — and reports how many frames survive.

It's a pure-software stand-in for tc netem: no network, no root, runs anywhere punktfunk-core builds. Use it to sanity-check the FEC before reaching for the real punktfunk/1 harness (which adds tc netem jitter/reorder on the UDP path).

cargo run -p loss-harness        # from the repo root

Part of the measurement tooling (punktfunk-planning: implementation-plan.md §10), alongside latency-probe.