NetVM: NODES.md carries the full per-profile persistent map
This commit is contained in:
@@ -1,9 +1,18 @@
|
||||
# NetVM nodes
|
||||
|
||||
Registry: which node egresses where. Sharing an egress identity is a
|
||||
designed choice — record the reason.
|
||||
Per-profile persistent map: **profile = node = Warp identity = deterministic
|
||||
network slot (veth IP, CDP port) = consistent egress IP.**
|
||||
|
||||
| node | netns | warp identity | egress IP | tail IP | shared with / reason |
|
||||
|------|-------|---------------|-----------|---------|----------------------|
|
||||
| tp | warp-tp | /etc/netvm/tp.conf (wgcf, 2026-10-03) | 104.28.203.246 | — | laptop; orchestrator + first node; UP, handshake+egress verified 2026-10-03 |
|
||||
| smoke | warp-smoke | /etc/netvm/smoke.conf (wgcf, 2026-10-03) | 104.28.203.246 | 100.64.120.18 | laptop; dedicated test rig (chrome-box profile smoke); UP, handshake+egress+CDP+muse.ai verified 2026-10-03 |
|
||||
Egress IPs may overlap between nodes (same Cloudflare colo / anycast exit).
|
||||
That is expected and fine. What persists — and what is mapped here — is the
|
||||
per-profile pattern: each chrome-box profile keeps its own identity, its own
|
||||
netns, its own veth/CDP slot, and its own consistent egress. One account, one
|
||||
stable network presence.
|
||||
|
||||
| profile/node | netns | warp identity | veth IP | CDP port | egress IP | tail IP | notes |
|
||||
|--------------|-------|---------------|---------|----------|-----------|---------|-------|
|
||||
| tp | warp-tp | /etc/netvm/tp.conf (wgcf, 2026-10-03) | 10.201.149.2 | 9277 | 104.28.203.246 | — | laptop; orchestrator + first node; UP, handshake+egress verified 2026-10-03 |
|
||||
| smoke | warp-smoke | /etc/netvm/smoke.conf (wgcf, 2026-10-03) | 10.201.87.2 | 9410 | 104.28.203.246 | — | laptop; dedicated test rig (chrome-box profile smoke); UP, handshake+egress+CDP+muse.ai verified 2026-10-03 |
|
||||
|
||||
CDP: `http://<veth IP>:<CDP port>/json/list` from the host, or
|
||||
`ssh -L <port>:<veth IP>:<port> <user>@<tail IP>` for remote automation.
|
||||
|
||||
Reference in New Issue
Block a user