Repository navigation
minvmd: measure the host loopback before handing a reserved-range address #1818
Description
Problem
On a VM-backed macOS host, minvmd hands a box's registration a slice address from the reserved local range (127.0.64.0/24) without measuring whether the host loopback can bind it. On a stock macOS host the range is not installed, so a box published at the handed address fails its attach: the host gvproxy is asked to bind a declared port at an address the loopback refuses (EADDRNOTAVAIL).
#1798 guards the daemon side: a handed reserved-range address is published only while the host publish surface's range verdict has not landed Absent, and the box falls back to the 127.0.0.1 interim (NET-123's absent arm) otherwise. The hand itself is still unmeasured at its source.
Wanted
minvmd hands a reserved-range slice address only after its own bind probe on the host loopback vouches for the range, and hands no range address (so the daemon publishes the interim) when the probe fails. A test covers both arms.
Activity
fix(net): re-point the window's publishes when the verdict lands
feat(minimald): bind declared ports before the name and refuse unpubl…
norrietaylor commentedon Oct 31, 2026
Closing in the 2026-10-31 backlog triage: the work has shipped.
Evidence: minimal#2332 (merged; 'informed by #1818') makes minvmd allocation probe the address with a TcpListener bind and hand 127.0.0.1 when the bind is refused. Both arms are tested: an_unbindable_host_is_handed_the_interim_and_the_book_stays_empty and a_host_that_becomes_bindable_hands_out_range_addresses_again.
Two independent reviewers checked this closure; neither refuted it. Reopen if it's wrong.