Issues 140 and 141: an endpoint's reach, and a forward chain that does not follow the modules #169

Merged
mesh-admin merged 1 commits from issue/140-endpoint-reach-and-141-forward-chain into main 2026-09-28 20:58:03 +00:00
1 Commits
Author SHA1 Message Date
jschoubben dcdfcf104e Issues 140 and 141: an endpoint's reach is declared nowhere, and the forward chain follows constants instead of the modules
Found preparing the control-node's convergence. Reach is settled independently by
the filter, the proxy's names and the certificate authority, so "this must not be
public" cannot be written and a public certificate is obtained regardless. And the
forward chain allows two hardcoded ranges plus a typed list, though the mesh
already knows which networks exist because its own modules declared them — a range
wide enough to keep four of them would have forwarded two predecessor leftovers too.
2026-09-28 22:57:38 +02:00