Johnathan Corgan
6a564e26ac
Everything the release needs except the version number, which stays at 0.5.0-dev until the tag. The changelog entry covers only the work that is new on this line. The point release's forty-six entries arrived under their own heading with the forward merge and are left alone; the twenty that remained are regrouped by topic and eight more added for changes no entry covered. Three of those eight matter to someone upgrading. Five root modules and four re-exports left the public library surface and Node::connections narrowed, none of it recorded anywhere; the entry names what to use instead and distinguishes the removed connection-phase enum from the Noise type of the same name, which is a different type that still exists. Tracing targets moved, so an existing RUST_LOG filter stops matching rather than erroring. And the handshake resend interval key no longer governs the first resend, which is now a constant, though it still governs later ones. Seven more entries cover the work that landed after the first content pass was written: the experimental native datagram API, the fipsctl probe diagnostic, per-instance transport addressing, the app-owned UDP socket seam, and the connect, disconnect and path-MTU fixes. The four bug fixes among them all reach the deployed line, so the release notes no longer claim this release carries exactly one fix for a shipped bug; it carries four. There is no security section, because after the split every security entry belongs to the point release. The release notes say so plainly rather than leaving a reader upgrading across both releases to conclude this one carries no security work. The notes are organized by audience, since the release spans OpenWrt routers, embedders, FreeBSD, and the existing platforms, and a single list serves none of them. The native datagram API is given a section of its own rather than folded into the embedding seam: it is a client-facing API rather than a way to host a node, and its one rule with no Berkeley-socket counterpart, that the v1 wire carries no half-close, needs to be somewhere a client author will read it. FreeBSD is advertised as supported on x86_64 only, stated wherever the platform appears. Android is advertised as an embedding seam and not as a supported platform: a compile-gated library surface with no artifact and no host application guide. The configuration table rename is carried through every shipped file that taught the old spelling: nine documentation files, the OpenWrt sample config and a test generator, twenty-two sites in all. Guides written this same cycle were among them, which is how the omission was found. The documentation that arrived with the native API was checked for the same omission and was already clean. The compatibility tests keep the old spelling deliberately, since they exist to test the fold. The changelog section is the fold of master's [Unreleased], not a snapshot of it. An earlier version of this commit took a copy that then drifted, so each section ended up holding a bullet the other did not and re-folding them would have picked a winner silently. Both causes were fixed on master instead — the NixOS module had never been recorded there, and the pre-release batch of fixes was new — so [Unreleased] is a strict superset and this is a copy rather than a merge. [0.5.0] carries all forty-six bullets byte for byte, [Unreleased] is empty, and [0.4.2] is untouched, checked by hashing it against master's copy. The BLE work landed after the content pass and gets one summary entry in the changelog and one section in the release notes rather than nine bullets: the ble_available gate replacing target_os = "linux", packet-boundary recovery for stream-oriented backends, peer recognition by node identity instead of a rotating link address, the L2CAP PSM moving into the backend seam and onto the advertisement, the embedder-supplied Android radio, bounded probe retry, and inbound handshakes moved off the accept loop. The two release-notes copies no longer share their link paths. Relative links resolve from one directory only, so the seven written for docs/releases/ all 404ed from the root copy. The root copy now uses paths from the repository root and the versioned copy keeps the ../ form; both sets were resolved against the tree. The same two links are broken the same way in the v0.4.0 through v0.4.2 notes, left as shipped history. The contributor tallies are re-derived against maint..HEAD rather than adjusted: twenty commits from outside the project and 171 from me, with Arjen at fifteen and fr34aky at two. An earlier count of twelve and 138 was carried from a measurement taken three days before this content was written, and the BLE branch widened the gap after it. Arjen's NixOS flake module, the UDP sin6_scope_id fix and most of the BLE rework were uncredited, as was fr34aky's L2CAP PSM seam. They want one last re-derive at tag time if anything lands before the tag. A sweep of all 99 tracked markdown files against the tree corrected fifty-three of them. Four told the reader to run a build.sh that does not exist; the only harness builder is testing/scripts/build.sh. The BLE build prerequisites were described as optional on the strength of a probe that build.rs does not perform, and bluez was named a build prerequisite when libdbus-sys asks only for libdbus-1-dev and pkg-config and bluez is the runtime daemon. Link cost is the primary sort key in next-hop ranking, not reserved for future use; Ethernet runs on macOS as well as Linux; the BLE MTU is the L2CAP CoC MTU rather than a negotiated ATT_MTU; effective Ethernet MTU is 1497; the LAN discovery subsystem is src/mdns and eight citations still named a src/discovery that never existed here. The connectivity states in three tutorials were invented, and their jq filters matched nothing including healthy peers. One command filtered on a literal fd97: address prefix, which only the first byte of fixes, so it returned empty for all but one reader in 256 and every later step using the variable failed silently. transports.tor.advertise_on_nostr was undocumented despite being validated against node.rendezvous.nostr.enabled. The transport design document gains the BLE section it never had, written from the source: the backend cascade and its compile_error tripwire, the platform gate, the PSM advertisement wire layout and the byte budget that forces a 16-bit service-data key, and the probe and admission bounds. Three source files carried the same class of staleness and are corrected with the documentation: the OpenWrt ipk usage line and Makefile error text both named a packaging/openwrt that does not exist, and chaos.sh parsed --subnet without listing it. Folded in with the content commit, having been prepared alongside it: The three GitHub Action pins that had gone stale. Every third-party action is pinned to a commit SHA, nothing reports that a pin has aged, and re-resolving all ten against their tags found dorny/test-reporter@v2, taiki-e/install-action@v2 and vmactions/freebsd-vm@v1 had moved. The three install-action@nextest references stay unpinned, since that action reads the tool to install from the ref name. check-action-pins.sh passes at 75 references and all nine workflow files parse. The lockfile refresh, which is the mutating half of the dependency sweep. Thirty-six packages move to their latest semver-compatible versions and every one is transitive; nothing declared in Cargo.toml changes version. No advisory forces any of them. It was taken before the validation battery, because a gate run against a lockfile that later moves proves nothing about what ships. The sha2 0.10 to 0.11, hkdf 0.12 to 0.13 and bech32 0.11 to 0.12 majors, three of the four deferred at v0.4.0 for change surface rather than security. All three land with no source change. sha2 and hkdf must move together, since both depend on digest 0.11, and neither changes an algorithm. That matters because the chaining-key KDF in the Noise handshake is built on Hkdf::<Sha256>, where an output change would be a wire break rather than a compile error; no known-answer vectors exist for that path, so the wire-compatibility gate is what covers it. secp256k1 0.31 is deliberately absent, since nostr's own requirement would leave two copies of the ECC library in the tree. The README support matrix, rebuilt as one feature table broken out by Linux variety. A single Linux column hid that Debian, Ubuntu, Arch and NixOS are one glibc build differing in packaging, that OpenWrt is musl and drops BLE, and that Android is not a daemon platform. Transport rows sort by how many platforms carry them. A Native API row reads its platform set from the cfg gates. The installer row becomes a package format row naming the artifact, and only the .deb is exercised per release. Four changelog and release-note gaps the BLE re-walk found: a Bluetooth LE bullet stranded inside the released 0.4.2 section, a missing Fixed entry for the scan and probe loop counting a pool-refused connection as an established link, the unnamed embedder call that installs an application-owned radio, and the fact that stopping the transport now stops scanning as well as advertising. Three release-document gaps found walking the unsurveyed commits: the UDP reuse-flag fix stated in the direction opposite to the one it was made, with the silent second-daemon bind it prevents left unsaid; the corrected native-API socket paragraph carried into both release-note copies, which still named SOCK_SEQPACKET on FreeBSD and two kernels where three are handled; and the coordinate-cache hardening, which shipped with no text anywhere despite adding four operator-visible status fields. That last entry states plainly that the checks are mitigations and not a closure, since the coordinate is still not authenticated. Also folded in, the documentation pass that followed the content commit: A stage-pipeline diagram for the probe, embedded in the fipsctl reference under the five-stage list. It draws the five stages left to right with each stage's failure reasons below it, and the bypass that skips both lookup stages when the coordinates are cached or the target is a direct peer. Its branches come from the probe state machine rather than from the report, so the path stage is drawn as the one failure that does not stop the probe. A rewrite of the README's "What FIPS does" section. It now opens with what a machine running FIPS gets, rather than with the two deployment modes, and gives the self-organizing and permissionless property its own paragraph since it holds for both modes. A regrouping of the README's feature list into the mesh, getting traffic onto it, and running a node, with a bullet added for the native datagram API, which had none despite sitting in the support matrix. The Quick start now leads with the released packages rather than a source build. It also fixes a real defect: the package enables fips.service and fips-dns.service and starts neither on a fresh install, so .fips name resolution was silently dead until the next reboot and neither page said to start the service. A rewrite of the release notes. They opened with seven subsections of upgrade caveats and reached the first feature two hundred lines in; they now open with a summary of the release and elaborate below it in the same order. Android is stated as supported through an embedded crate rather than as a standalone daemon, consistently across all three documents. The OpenWrt pair is corrected: it is 802.11s between routers with FIPS supplying encryption, authentication and routing, plus a convention of an open !FIPS SSID a client joins over WiFi, not meshing over a router's own radios. The probe's path output is described as the least-common-ancestor walk, which is the worst-case fallback route rather than the route a packet takes. Detail that did not change what a reader does was cut from the notes and kept in the changelog.
FIPS mesh-reliability lab
Local reproduction infrastructure for chronic CI integration-test flakiness. The goal: turn "happens occasionally on GitHub Actions" into "reproduces deterministically under controlled local pressure," then fix on bedrock instead of bumping timeouts.
Quick start
Prerequisites — same as testing/ci-local.sh:
- Docker daemon reachable.
fips-test:latestandfips-test-app:latestDocker images built. The easiest way to (re)build them is to runtesting/ci-local.sh --build-onlyonce after a fresh checkout or after touching the daemon source — the lab itself does not rebuild between reps.- Python 3 with
pyyamlandjinja2installed for the chaos suites (pip3 install --user pyyaml jinja2). stress-ngon the host for pressure profiles other thanidle(sudo apt-get install stress-ng).
Simplest invocation — single rekey rep on the idle profile (no CPU
pressure), output under a timestamped subdir of runs/:
bash testing/mesh-lab/run-loop.sh rekey
Twenty reps under the github-runner-equivalent pressure profile (the canonical Phase 1 acceptance-gate shape for the rekey Phase 5 flake class):
bash testing/mesh-lab/run-loop.sh rekey --reps 20 --profile github-runner-equivalent
The harness writes per-rep diagnostics to
<runs-base>/runs/<timestamp>/rep-NN/ (raw logs, container state,
exit codes) and a per-rep summary.json plus an aggregated
<runs-base>/runs/<timestamp>/summary.json at the end. Where
<runs-base> lands is controlled by the FIPS_MESH_LAB_RUNS_DIR
environment variable (see below); by default it is the in-tree
testing/mesh-lab/ directory. Raw artifacts are gitignored — they're
big and per-developer. The summary.json shape is compact so triage
doesn't require holding the raw log stream.
Suites supported
Initial target set:
rekey,rekey-accept-off,rekey-outbound-only— rekey-suite Phase 5 post-second-rekey connectivity flake class.nat-lan— two-node NAT-traversal handshake-completion flake class.bloom-storm— chaos scenario; covers thebloom_send_rateper-node ceiling exceedance class (single node spiking above the ceiling while peers stay well under). Note that chaos uses its own python sim runner (not docker-compose), so the mesh-labcompose-resource-limits.ymlandcompose-trace.ymloverrides do not apply to this suite; per-rep evidence comes from the capturedtest-output.logand the parsedsignature.json(which extracts thebloom_send_rateandmin_parent_switchesassertion outcomes plus per-node delta distribution).
Adding more is straightforward — see the dispatch_suite function in
run-loop.sh.
Pressure profiles
Defined in pressure-profiles.sh:
idle— no pressure. Baseline; should produce zero failures on a healthy mesh.light— placeholder. Will be calibrated.github-runner-equivalent— placeholder. Will be calibrated to approximate the headroom anubuntu-latestGitHub runner has while also juggling four parallel package-build workflows (estimate: 2-core / ~7 GiB total, so 1 stress-ng worker + memory ballast). The initial calibration target: this profile must reproduce the rekey Phase 5 flake class at ≥20% rate over 20 reps with mechanism-match.heavy— placeholder. Worst-case pressure for stall-finding work.
Environment-variable knobs
The harness reads optional environment variables that shape what each rep does, set them in the invoking shell:
-
FIPS_MESH_LAB_NETEM— netem argument string (e.g."delay 10ms 5ms 25% loss 1%"). When set, the harness runstc qdisc add dev eth0 root netem <args>inside each fips-node container aftercompose up. Bridge-level qdisc on the docker network does not shape inter-container traffic (Linux bridges forward port-to-port without packets traversing the bridge interface's egress qdisc), so per-container egress is the correct injection point. -
FIPS_MESH_LAB_TRACE— when set to any non-empty value, the harness layers a suite-specific trace-RUST_LOG compose override on top of the base stack. Module sets are per-suite:- rekey / rekey-accept-off / rekey-outbound-only —
rekey,handshake,forwarding,session,encrypted,mmp(viacompose-trace.yml). - nat-lan —
fips::nostr,transport::udp,node::lifecycle,handlers::handshake,dataplane::forwarding(viacompose-trace-nat.yml, picked up bytesting/nat/scripts/nat-test.shthrough theFIPS_NAT_EXTRA_COMPOSEenv-var hook). - bloom-storm — no compose override applies; chaos uses its own python sim runner.
Use only when capturing primary failure-moment evidence for mechanism investigation — log volume increases substantially. Without this knob, daemon logs only capture state transitions and not per-datagram forwarding decisions, which makes evidence collection for routing-state stalls effectively impossible.
- rekey / rekey-accept-off / rekey-outbound-only —
-
FIPS_BLOOM_STORM_CPUSET— comma-separated CPU set for the bloom-storm dispatch's container-pinning sidecar (default0,1). The sidecar polls forfips-*containers as the chaos sim spawns them and appliesdocker update --cpuset-cpus <set>to each, mimicking the 2-core constraint of a GHAubuntu-latestrunner. Set to a wider set (e.g.0,1,2,3) to relax, or to the empty string to disable the sidecar entirely. Only applies to thebloom-stormsuite; other suites ignore it. -
FIPS_NAT_LAN_CPUSET— comma-separated CPU set for the nat-lan dispatch's container-pinning sidecar (default0,1). Same shape asFIPS_BLOOM_STORM_CPUSET, but the sidecar polls forfips-nat-lan-*containers and applies the cpuset as the compose-up creates them. The mesh-labcompose-resource-limits.ymloverlay is rekey-family service-name-specific (servicesrekey-*/rekey-accept-off-*/rekey-outbound-only-*), so it does NOT constrain the nat-lan containers; the sidecar fills that gap. Only applies to thenat-lansuite; other suites ignore it. -
FIPS_MESH_LAB_TRACE_TREE— when set to any non-empty value, layerscompose-trace-tree.ymlover the rekey-family compose stack to bumpRUST_LOGto trace level onfips::node::tree,fips::tree,fips::node::handlers::mmp, andfips::node::handlers::handshake. Distinct fromFIPS_MESH_LAB_TRACE(rekey/forwarding/session/encrypted at trace); targeted at tree-partition race investigation during multi-peer startup. Mutually exclusive withFIPS_MESH_LAB_TRACEin practice — both env vars layer their overlay, but the second one's per-service environment replaces the first's. Only applies to the rekey-family suites. -
FIPS_MESH_LAB_NO_RESOURCE_LIMITS— when set to any non-empty value, omits thecompose-resource-limits.ymloverlay for rekey-family runs. Default behaviour keeps the overlay engaged so rekey-family lab reps stay pressure-matched to a GHAubuntu-latestrunner. Set this for unconstrained characterization where the goal is to surface a race or scheduling artefact rather than reproduce CI pressure. Only applies to the rekey-family suites; other suites ignore it. -
FIPS_MESH_LAB_RUNS_DIR— root directory for harness output (theruns/<timestamp>/tree). When unset, the harness falls back to an in-tree path undertesting/mesh-lab/and prints a warning to stderr naming the variable and the fallback location. Set this to a path outside the source tree (e.g./var/tmp/fips-mesh-labor a path on a separate disk) to keep gigabyte-scale per-rep artefacts out of the checkout.
Example:
FIPS_MESH_LAB_TRACE=1 \
FIPS_MESH_LAB_RUNS_DIR=/var/tmp/fips-mesh-lab \
bash testing/mesh-lab/run-loop.sh rekey-accept-off \
--reps 20 --profile github-runner-equivalent
Recipes
recipes/<flake-id>.yaml files are commit-pinned reproduction recipes
the harness consumes. Each recipe declares the source SHA, the suite,
the pressure profile, the rep count, and the expected mechanism-match
rate, so a future operator can confirm "yes the lab still reproduces
this flake at the documented rate" with one command. None exist yet —
they're authored as concrete reproductions surface.
How this differs from testing/ci-local.sh
ci-local.sh runs each suite exactly once in sequence (chaos
scenarios in parallel up to a job slot count), produces a pass/fail
matrix, and is the canonical "did anything regress" gate. The
mesh-lab runs the same per-suite test scripts (it does not
reimplement them) but in a loop, with deliberate host pressure
applied, and with rich per-rep diagnostic capture. They share the
Docker images and the test scripts.
When in doubt, debug a single suite via ci-local.sh --only <suite>
first to confirm the suite is healthy on idle, then graduate to the
mesh-lab when you want to chase a flake.