jochen
0f6986aead
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.
48 lines
828 B
JSON
48 lines
828 B
JSON
{
|
|
"module": "netcheck",
|
|
"version": "1",
|
|
"tools": [
|
|
"netcheck_tcp",
|
|
"netcheck_dns",
|
|
"netcheck_http",
|
|
"netcheck_listening"
|
|
],
|
|
"replaces": {
|
|
"netcheck_listening": [
|
|
"ss -lunt",
|
|
"ss -ltn",
|
|
"netstat -lnt"
|
|
],
|
|
"netcheck_dns": [
|
|
"dig",
|
|
"nslookup"
|
|
]
|
|
},
|
|
"build": {
|
|
"artifacts": [
|
|
{
|
|
"name": "tools-go",
|
|
"kind": "bundle",
|
|
"language": "go",
|
|
"system": "arch",
|
|
"from": "cmd/netcheck",
|
|
"binary": "netcheck",
|
|
"loads": [
|
|
"netcheck"
|
|
]
|
|
},
|
|
{
|
|
"name": "tools-typescript",
|
|
"kind": "bundle",
|
|
"language": "typescript",
|
|
"entrypoints": [
|
|
"tools/index.js"
|
|
],
|
|
"loads": [
|
|
"tools/index.js"
|
|
]
|
|
}
|
|
]
|
|
}
|
|
}
|