8000 minimald: a VM guest gives the node plane and the host-address cohort one source address (NET-078, NET-138) · Issue #3080 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

Navigation Menu

minimald: a VM guest gives the node plane and the host-address cohort one source address (NET-078, NET-138) #3080

Open

Description

@msample

Where: crates/minimald/src/main.rs:929-943 at d7c85f6.

What spec 18 requires.

  • NET-078: "THE SYSTEM SHALL classify node-plane traffic and the host-address cohort separately with distinct source identities." Its note keeps the SNAT rules in force on a VM-backed host while un-enrolled, "since the host-side helpers are the egress gateway there (design §7.1)".
  • NET-138 gives the host-side table separate rows for "the node itself and the host-address cohort". The gate (NET-081) decides by that table.
  • Design §4.1: workload and node-plane traffic "never share an identity: host_ip boxes do not inherit the baseline set".

What the code does. On a microVM guest, the classifier render gets the same address for both identities, the guest's own 100.64.255.253:

// NET-078's two source identities are the guest's own address on a guest —
// the cohort and the node plane share it — but the render is told them as
// the two inputs they are, never left to assume.
cohort_address: identity,
node_plane_address: identity,

Native hosts are not affected. NET-078's sub-requirements keep the two apart there by cgroup match.

What it costs. A host-address box's own rules still bind it: the guest decides each box on its own cgroup before translation (NET-079). What is lost is the layer outside the guest:

  • One source address cannot select between NET-138's node row and cohort row. Nothing states which row the gate applies to .253.
  • The gate cannot keep the node-plane rules away from the cohort, as §4.1 requires.
  • Records at the gate and at the node-local BEP cannot tell minimald's flows from a host-address box's flows.

The address. The gominimal/arch#108 ruling (2026-11-06) reserves a host-ip cohort address in every node block, below the BEP peer. In the local plan its working value is 100.64.255.251.

Ask. Give the cohort its own address on a guest, and translate the two classifier matches to the two addresses, as NET-078's note says. If the shared address is a deliberate interim, record it in spec 18 as a residual, with its cost and an end, and state which NET-138 row the gate applies to the shared address.


This is a residual of epic #1437 (NET).

Activity

  1. norrietaylor commented on Nov 20, 2026

    @norrietaylor
    Member

    Task

    Source: #3080

    Plan block
    ### D3080 — On a microVM guest, node-plane traffic leaves as 100.64.255.253 and the host-address cohort leaves as its own reserved address 100.64.255.251
      kind: task
      size: M
      est: 180 code, 160 tests
      executor: agent
      origin: residual
      epic: 1437
      layers:
        - switch:
          - crates/switch/src/lib.rs: adds SwitchSubnet::host_ip_cohort_address below the BEP peer, and moves last_ptask below it so no lease takes it
          test: cargo test -p switch host_ip_cohort_address
        - guest:
          - crates/minimald/src/main.rs: passes the cohort address as cohort_address and daemon_ip as node_plane_address to GuestRender
          - crates/minimald/src/guest.rs: adds the cohort address to eth0 beside the daemon address, so SNAT replies return to the guest
          - crates/minimald/src/net/switch.rs: lets the node relay admit frames from the cohort address as well as the daemon address (NET-084)
          - crates/minimald/src/net/classifier.rs: tests that the guest render SNATs the cohort mark and the node-plane mark to two distinct addresses
          test: cargo test -p minimald guest_render_gives_cohort_and_node_plane_distinct_addresses
        - gate:
          - crates/minvmd/src/box_registry.rs: keys the NET-138 cohort row by the cohort address and the node row by the daemon address
          - crates/minvmd/src/net/egress_gate.rs: selects the cohort row or the node row by source address, so node-plane rules never apply to the cohort and records name each
          - crates/minvmd/src/net/bep_stub.rs: uses the cohort address as the cohort source in place of host_alias
          test: cargo test -p minvmd gate_decides_cohort_and_node_rows_by_source_address
        - spec:
          - docs/specs/18-spec-box-networking/18-spec-box-networking.md: states the guest cohort address for NET-078 and NET-138, and which row the gate applies to each address
          test: cargo test -p minvmd gate_decides_cohort_and_node_rows_by_source_address
      proof: On a VM-backed host, a flow from a host-address box reaches the gate with source 100.64.255.251 and the cohort row, and a minimald flow arrives as 100.64.255.253 with the node row.
    
  2. norrietaylor commented on Nov 20, 2026

    @norrietaylor
    Member

    /implement

  3. minimal-foundry commented on Nov 20, 2026

    @minimal-foundry
    Contributor

    Refused: A person needs to take it from here.

    branch agent/3080-on-a-microvm-guest-node-plane-traffic-leaves-as · epic #1437 · PR #3712

    round outcome job
    1 failed: A person needs to take it from here. b4ad0bb2
    2 refused: A person needs to take it from here.

    Updated 2026-11-21T01:51:44.349Z.

  4. minimal-foundry commented on Nov 20, 2026

    @minimal-foundry
    Contributor

    That /implement is held, not dropped. The container platform had no instance to give the coder: its pool of prepared containers was full, which happens most just after a deploy. It is asked again every 10 minutes for up to 30.

    Nothing to type again: the command gets a rocket when its coder starts, or a refusal that names the reason.

    What the platform said

    could not start the coder: Error: there is no container instance that can be provided to this durable object

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority:should-haveShould be done. Applied by the inbox-route classifier or a human.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0