Issue 081 opened (a cache consumer does not use its login); 079 and 080 diagnoses carry the review's consequences

2026-09-22 02:04:29 +02:00
parent f760bf632c
commit 35e44c3e5e
3 changed files with 43 additions and 0 deletions
@@ -22,3 +22,10 @@ machine with an address, while the resolver's "on the private network" is a mach
 runs the module that puts it there. The names follow the resolver's rule now — one predicate,
 used by both — held by a controller test that unassigns one machine's networking and reads the
 names back.
+
+Two consequences of the one predicate, on review. The filter's "from the mesh" set is that same
+set now, so a rule admits exactly the machines the mesh names. And a machine whose assigned set
+fails to resolve is no longer on the network in the mesh's eyes: its name leaves every other
+machine's hosts file and every resolver's zones on the next push, and the mesh's report of that
+machine's failure is what says why — the stated preference for a name that fails at once over a
+connection that hangs, at the cost of one machine's failure being visible mesh-wide.