Skip to content
SHC Docs

Layer 1. Mesh

Layer 1. Mesh. Layer page.

mesh0 is the node plane. It carries rqlite, the internal RPC, and the transfer layer between nodes. shc0 carries containers. Both dial a peer’s underlay address.

The mesh waits on the edge deployment and on nothing else above it. Every node joins through the edge on TCP 443 (ruling D1, register row A-07).

ce modules/mesh/mesh.go names the device mesh0 and the listen port nodeports.MeshListen (UDP 4244). Each node keeps its mesh0 private key; the public key goes on the mesh_peer row.

Enrolment is POST /api/join/node.enroll on TCP 443. The peer-table fetch is served only through that public join route (ce modules/mesh/peer_table_server.go). When the store is behind, the node retries the HTTPS join entrypoint (ce modules/mesh/doctor.go). The join client defaults a bare host to port 443 (shc modules/cluster/join_client.go).

The join route serves five functions and no others: node.enroll, mesh.peer_table, underlay.members, underlay.probe.arm and underlay.probe.result. tests/unit/ci/join_surface_test.go holds that list.

Ruled, not on this pin: a second tunnel wrapped around mesh0.