MeshLAN tested by Argusic Runner

What the test found

Go toolchain and Nebula installed; tests pass 56/56; the MeshLAN server binary built and its HTTPS control plane served /admin 200, issued a verified device certificate via /v1/pair, returned admin sessions and heartbeat service mapping 200, and the node agent enrolled successfully; only the Nebula overlay itself did not run because the container lacks /dev/net/tun.

TUN unavailable in container, so Nebula overlay did not start; the HTTPS control plane (pairing, admin, heartbeat, node agent) all verified. Node-agent auth worked only after recovering the true secret from the state hash, indicating a printed-vs-stored mismatch to review.

Argusic installed MeshLAN in 3 minutes and launched it; verification reached Verified running for real. 4 of 4 recorded errors were worked through (see the timeline below).

Runsall runs of MeshLAN

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.