Repository navigation
v0.2.0
Reverse connect. The node can dial out to a hub instead of listening: a machine behind NAT or someone else's firewall is reachable with zero inbound ports and no SSH. Node and hub are the same binary, mutually authenticated with HMAC-SHA256 over fresh nonces from both sides, with ping/pong and jittered reconnect. Clients reach each node through the hub at /n/<name>/mcp. TLS on the link is optional.
Also in v0.2.0:
--versionand--help; unknown arguments are rejected- duplicate node names are probed before takeover: a live link keeps its name, the newcomer is refused
- listen sockets use SO_REUSEADDR without SO_REUSEPORT, so a second listener on a busy port fails loudly
Numbers (i3-9100F, N=100 cold cycles, medians): 1.9 ms to first MCP response, 0.62 MiB idle RSS, +288 KiB per extra connection, one 8.70 MiB static binary. Method and reproduction: BENCHMARKS.md.
Full Changelog: v0.1.2...v0.2.0