Files
mesh-catalog/modules/netcheck
jschoubben ac4ed46359 M1: every manifest says its class; the delivery modules' stores name their caps
A module that claims a seat is core, one that claims none a leaf (141
manifests; the build modules and the registry are the other developer's).
The forge module's, the gate's and the sweep's states each name 8 MiB, and
their findings stream 8 MiB for 7 days.

Builds: design 47 H2 §810, §812, §783, §820; H-A-394 (1), H-A-411 (1), (2), H-A-378
2026-11-22 01:01:26 +01:00
..

netcheck

The machine's own network checks as tools: a TCP connect (netcheck_tcp), a DNS lookup of the machine's resolver or of one named (netcheck_dns), what listens here (netcheck_listening), the private network's peers (netcheck_tunnel), and whether a URL answers (netcheck_http). netcheck_request makes one HTTP request (GET, HEAD or POST, with headers and a body of at most 256 KiB) and answers the status line, every response header and the body (at most 1 MiB, with a flag saying when it was cut), reporting redirects without following them and speaking only http and https, refusing any connection to this machine's own loopback, unspecified or link-local addresses (checked on the address dialled, so names that resolve there are refused too) and using no proxy, so a service's live answers can be captured (hq issue 1643).