4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	4fc769ed29	Show the tunnel's peers as each machine sees them, and say on the bus when they move (hq issue 522) ... ace's tunnel leg lost most packets while its own check called the tunnel healthy, and nothing on the mesh could say which address and port the hub saw for each peer, which is what tells a home router's port mix-up from anything else. netcheck_tunnel answers each peer's endpoint, last handshake and traffic, never a key, and netcheck now says when a peer's endpoint changes or its handshake goes stale or fresh again.	2026-10-11 23:50:17 +02:00
jschoubben	a6a9a818d2	Answer the review of hq issue 348's catalogue change ... - The dnsmasq watch restarts only a unit that runs, without waiting for its start; a unit stopped, starting or failed is held and said (C2). - dnsmasq_resolve asks only an address the resolver listens on (C3). - Tests for the watch loop keeping its budget, a watch that wrote nothing or stopped looking, and a unit not running (C4). - A restart is remembered as said only once emitted, restarts made before the bundle started are said, and whether one helped is said (C5). - docker_events reads the runtime's whole buffer: complete when it is not full or reaches past the window, never a quiet machine read as lost (C6). - netcheck: refused read with errors.Is; tests for addresses and ports, and for a container named as docker knows it.	2026-10-09 15:25:45 +02:00
jochen	0f6986aead	netcheck: ask one named resolver, and list what listens here (hq issue 348) ... During the 2026-10-09 outage the control node's resolver stayed active while it no longer listened on its private address, and nothing on the mesh could ask that address a question or show which sockets were bound. netcheck_dns takes server (and tcp) to ask one resolver alone and say its response code; netcheck_listening reads the kernel's socket tables, as ss -lunt does, with the owning program where the tool's account may see it and a sentence where it may not.	2026-10-09 15:04:45 +02:00
jochen	7e9ef899c1	netcheck: one module, a Go tools bundle and a TypeScript one (hq ADR 0188, 0193) ... ADR 0193 says the node's runtime launches every served bundle over MCP stdio and knows no language, and ADR 0188 says one module may carry several bundles in any language. Nothing in the catalogue shows both at once: every tools bundle is TypeScript, and the only Go bundle is the runtime itself. netcheck is the smallest real module that does — read-only checks from a machine, worth having on their own: - tools-go (Go SDK go/v0.1.6): netcheck_tcp (one connect, nothing sent) and netcheck_dns (A/AAAA/CNAME/TXT/MX through the machine's resolver). - tools-typescript (@novox/mesh-sdk): netcheck_http (HEAD or GET, body neither sent nor read, redirects reported not followed, anything but http(s) refused). Both say loads; the module lists its tools. No container, no image, no env: nothing to be given, so the runtime's own words suffice.	2026-10-04 00:34:31 +02:00