D3570 — Declared ingress forwards bind at activation, stay bound for the box's lifetime, and unbind at release on every host · Issue #3578 · gominimal/minimal · GitHub
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switch
8000
ed accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
D3570 — Declared ingress forwards bind at activation, stay bound for the box's lifetime, and unbind at release on every host #3578
### D3570 — Declared ingress forwards bind at activation, stay bound for the box's lifetime, and unbind at release on every host
kind: task
size: L
est: 350 code, 300 tests
executor: agent
origin: bug
epic: 1437
layers:
- daemon:
- crates/minimald/src/box_actor/setup.rs: finalize binds the declared forwards on a native host too (in place of the host_ports_in_use probe), rolls back on a taken port, registers no name, and keeps the forwards
- crates/minimald/src/net/policy.rs: one activation bind for both hosts, and release_declared asks the switch to unexpose on a VM-backed host in place of the log-only branch
- crates/minimald/src/net/gvproxy_network.rs: finish_own_ip_attach and OwnIpAttach::release use the activation-held forwards and do not bind or unbind declared ports per spawn
- crates/minimald/src/box_actor/ports.rs: holds the declared forwards for the box's lifetime and unbinds moved declared ports on a VM-backed host as well
- crates/minimald/src/box_actor/host.rs: releases the box's declared forwards at box stop through release_declared_ingress
test: cargo nextest run -p minimald declared_ingress_bound_at_activation
test: cargo nextest run -p minimald release_declared_ingress_unbinds_on_vm_host
- vmhost:
- crates/boxes/src/core/switch_request.rs: applies a retraction of a port that the row at its own address declares, in place of Refusal::Unheld
- crates/minvmd/src/net/egress_gate.rs: forwards the box's withdrawal of its declared port to the switch and drops the forward from its ledger
test: cargo nextest run -p minvmd retract_of_declared_port_applied
test: cargo nextest run -p boxes retract_of_declared_port_applied
- spec:
- docs/specs/18-spec-box-networking/18-spec-box-networking.md: NET-121 and the S10a withdrawal rule say the bind is at activation and a declared port's withdrawal by its own box is applied
test: cargo nextest run -p minvmd retract_of_declared_port_applied
proof: An activation with a taken declared port fails and names the port and --ingress, a port taken after activation does not fail a later attach, and box stop on a VM host frees the ports at once.
Round 10 of 10 changed nothing: every commit this round put on the branch above e881930 is a merge of the base branch, so it carries no work of its own. #3603 is still open.
Activity
norrietaylor commentedon Nov 18, 2026
/implement
minimal-foundry commentedon Nov 18, 2026
Round 10 of 10 changed nothing: every commit this round put on the branch above e881930 is a merge of the base branch, so it carries no work of its own. #3603 is still open.
branch
agent/3578-declared-ingress-forwards-bind-at-activation-sta· epic #1437 · PR #3603d00f6efc83776eac79e5dc2a992761eb86db4ce91ada8826fae896c4bd3ec2869b38a82fUpdated 2026-11-21T01:19:44.556Z.