Skip to content

Release 2.2.1: dyode_in/dyode_out optional with transport: air - #10

Merged
nc-intezra merged 1 commit into
mainfrom
release-2.2.1
Nov 15, 2026
Merged

nc-intezra merged 1 commit into
mainfrom
release-2.2.1

Conversation

@nc-intezra

Copy link
Copy Markdown
Owner

Summary

Release 2.2.1, a small fix found during the first hardware test of transport: air: Ubuntu 24.04 → Raspberry Pi 3 over wfb-ng, with 20 MB and 30 MB files delivered with identical SHA-256.

With air there is no diode NIC, so the dyode_in / dyode_out sections can be left out of config.yaml. Two leftovers of those sections are fixed:

  • dyode check printed placeholder addresses (network: in 10.0.1.1 (eth0) -> out 10.0.1.2 (eth1)). It now prints network: not used (transport: air).
  • The local API's diode-NIC guard refused to listen on any address of the interface named in dyode_in/dyode_out. With the sections omitted, the default eth0 on the input side could refuse the box's real management NIC. The guard is now skipped for air; lidi is unchanged.

Also: a unit test for the guard on both transports, a note in docs/AIR.md, version 2.2.1, and a dated CHANGELOG entry.

Test plan

  • cargo fmt --check, cargo clippy --all-targets -D warnings
  • cargo test: 83 unit tests (1 new) and tests/air.rs
  • tools/check_release.sh v2.2.1 passes (dated 2026-11-15)
  • The trimmed config (no dyode_in/dyode_out) ran on real hardware with the 2.2.0 binaries
  • CI green on this PR
  • After merge: a human pushes tag v2.2.1

Generated by Claude Code

- dyode check prints "network: not used (transport: air)" instead of the
  placeholder addresses.
- The API's diode-NIC guard is skipped for air: there is no diode NIC,
  and the default interface name could refuse the real management NIC.
- Test for the guard on both transports; docs/AIR.md note; version 2.2.1,
  dated CHANGELOG.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018Q4FHhHAFgBUCsPf3UW67z
@nc-intezra
nc-intezra merged commit fd84e1b into main Nov 15, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants