MeshLAN

Self-hosted P2P-first virtual LAN, service sharing, multi-relay and AI automation built on Nebula.

Runssource: GitHubGoMITcommit 591f5f5593ef

Go, MIT licensed. The project labels itself: golang, mesh network, nat traversal, nebula, p2p, relay, self hosted and virtual lan.

MeshLAN runs. An Argusic agent installed it in 3 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

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.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.20 (measured)
recorded runs
2
last tested
stars
250
forks
41
open issues
2
watchers
2
size
3 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing MeshLAN, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • printed MLNODE1 code secret does not match node-state secretHash; node agent returned 401 until I recovered the matching secret by recomputing the state hash3 minutes
  • go: not found in container1 minute
  • nebula/nebula-cert 1.11.x missing1 minute
  • Nebula child cannot open TUN: /dev/net/tun missing, no root1 minute
Install time
3 minutes
Cold machine to finish
19 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
go test -count=1 -v ./... exited 0 with 56 PASS/0 FAIL; curl -sk https://127.0.0.1:8443/admin returned 200; POST /v1/pair returned 200 and nebula-cert verify exit 0; POST /v1/admin/session returned 200; POST /v1/heartbeat returned 200; POST /v1/node/enroll returned 200 with enrolled:true
Model tokens used
319,696
Exact commit tested
591f5f5593ef
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**Gap (container limitation, not a code failure)**
- The Nebula child can't create a TUN device here (`/dev/net/tun` missing, no root): it logs `Faile…
**Errors encountered and fixed**
- `go: not found` → installed Go toolchain into `~/opt/go`.
- `nebula: not found` → downloaded Nebula 1.11.0 into `~/.local/bin`.
- Node agent rejected my first auth attempt because I used the token as printed; the printed code c…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 3…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 3, "errors": [{"msg": "go:…
tokens used
319,696

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 3 minutes, faster than the median of the 8 comparable projects Argusic has measured.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 9 golang projects Argusic has installed and timed, MeshLAN was the 3rd fastest to reach a running state, and 8 of 9 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 3 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.20
Argusic Runner1/3Did not run20.000.09

Topics (from GitHub)

golangmesh-networknat-traversalnebulap2prelayself-hostedvirtual-lanvpnwindows

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/MeshLAN.svg)](https://argusic.com/subject/meshlan)

Questions

Does MeshLAN run?
Yes. MeshLAN runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test MeshLAN?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 591f5f5593ef. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test MeshLAN?
The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does MeshLAN take to install?
3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does MeshLAN need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing MeshLAN?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does MeshLAN compare with the alternatives?
Of the 9 golang projects Argusic has installed and timed, MeshLAN was the 3rd fastest to reach a running state, and 8 of 9 reached one at all.
Where is the evidence for MeshLAN?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion