Skip to content

v0.2.0 — Wi-Fi groups both ways

Choose a tag to compare

@Resilum-owner Resilum-owner released this 04 Sep 19:23
· 39 commits to main since this release

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.