Skip to content

Releases

v0.2.3

Choose a tag to compare

@Resilum-owner Resilum-owner released this 11 Sep 19:22

The images this tag built

ghcr.io/resilum/resilum-core:0.2.3
ghcr.io/resilum/resilum-core@sha256:71d6870228455b9c607a402c035a2288879fdb18b581dd1eaab98d902029ddfd

ghcr.io/resilum/resilum-core-rngit:0.2.3
ghcr.io/resilum/resilum-core-rngit@sha256:338f0e3191a55571f3ad73af48958eee098528839387f31a85ce6284493a4c34

v0.2.2

Choose a tag to compare

@Resilum-owner Resilum-owner released this 09 Sep 20:30

The images this tag built

ghcr.io/resilum/resilum-core:0.2.2
ghcr.io/resilum/resilum-core@sha256:7f2bb218e19b4bf024d0a7d29e7b76395827125247751930e6e7c5c61ad11a65

ghcr.io/resilum/resilum-core-rngit:0.2.2
ghcr.io/resilum/resilum-core-rngit@sha256:b6a8da2bfc6d8bee07ec05c30120ebbf26c0bee8db998c1c9dd33a579ee01502

v0.2.1 — the radio hears

Choose a tag to compare

@Resilum-owner Resilum-owner released this 07 Sep 13:21

BLE

  • The driver read nothing back from the radio. It wrote commands and never
    collected events, so a scan started but its results were dropped, a peer that
    dialled us was never noticed, and GATT writes and notifications went nowhere —
    two nodes could not find each other over the radio at all. Discovery,
    disconnects, incoming subscriptions, incoming writes and notifications now
    reach the engine, and a node that dials a peer subscribes to its notify
    characteristic.
  • The beacon moved into service data, keyed by the service UUID, and is read
    from there in preference to the advertised name. A peer still announcing in
    its name is heard as before.
  • A failed handover to the radio no longer costs the session. It ran inside
    a Once, which a panic poisons for the life of the process, so the next
    attempt failed on the poison rather than on anything real.

Wi-Fi group

  • A group is raised only when there is a neighbour to raise it for. A node
    that heard nobody won the election against itself and hosted for an empty room.
  • The profile is deleted rather than left behind. One was created per
    activation and nothing removed it; a failure on the step after the radio came
    up dropped the teardown unrun, and the next tick tried again.

Covert

  • An acknowledgement for something never sent is refused — a peer could hang
    the engine with one out-of-range ack.

Deployment

  • Compose pulls the published images instead of building from source, and the
    README says plainly whether a node interoperates with a Python RNS network.

v0.2.0 — Wi-Fi groups both ways

Choose a tag to compare

@Resilum-owner Resilum-owner released this 04 Sep 19:23

A node can now enter a Wi-Fi group as well as raise one, it declines both when
that would cost it the only way out, and three silences that hid failures are
gone.

Wi-Fi groups

  • Hosting raises a P2P group, not an access point. A single radio cannot
    hold a station and an access point at once on most hardware, so raising one
    the old way tore down the node's uplink. The raise now reports which
    interface the group actually landed on, because a P2P group gets its own.
  • Joining exists at all. Entering a group was only reachable over the FFI,
    where the caller handed us an already-connected socket. Nothing on this side
    associated with a group or dialled its owner, so two machines could meet only
    if the right one won the election.
  • Neither is done at the cost of the only way out. A node whose default
    route runs over the radio the group would take loses every other transport by
    taking part, and a host that loses its uplink by hosting defeats the rank that
    chose it. Such a node reports itself unfit to host, so the election passes it
    over, and declines to join for the same reason.

Silences

  • The BLE scan restarted every five seconds, spending six starts per thirty
    where the platform allows five, after which it keeps the scan registered and
    quietly delivers nothing. Two nodes advertised at each other and neither
    noticed.
  • Covert over ICMP could not open its socket on a host whose
    net.ipv4.ping_group_range is empty — the common default — because the client
    only tried the unprivileged socket, which answers to that setting rather than
    to capabilities. It now falls back to a raw socket and names both refusals
    when neither works.
  • Advertising failures were discarded. The radio library now waits for the
    stack to confirm and reports what went wrong; that result is no longer thrown
    away.

Also

  • Interface combinations from the kernel were read without their per-group
    limit, so two roles sharing one slot looked concurrent.
  • A node advertises only the mirrors it actually serves, and asks for the ones
    it lacks from whoever already advertises them.
  • Two structural lint rules: a test-only module goes last in its file, and a
    unit test that stands up a whole node belongs with the integration tests.
  • The BLE library comes from our fork while two fixes wait upstream: an Android
    adapter name that was taken and never given back, and service data.

Deploying a node with ble or wifi_group set now needs the host's system bus
and root — BlueZ serves GATT to root alone, and NetworkManager sends its
settings change to polkit for everyone else. The compose defaults name both.