vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs(network): dedupe UDS control-plane explanation

Browse source
This commit is contained in:
iris 2026-08-15 11:46:26 +02:00 • committed by mara
commit b15e0e973c
1 changed files with 5 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/network.md
View file

@ -245,12 +245,11 @@ wiring is runtime:
It is ordered `before` the harness (`hive-ag3nt`), the matrix daemon, and It is ordered `before` the harness (`hive-ag3nt`), the matrix daemon, and
`tea-login` so the resolver is correct before the first DNS lookup. `tea-login` so the resolver is correct before the first DNS lookup.
**Why isolation is safe**: all hive-c0re communication goes **Why isolation is safe**: hive-c0re's control-plane sockets are unix
through unix domain sockets (`/run/hive/mcp.sock` for agent requests, domain sockets bind-mounted into containers, not network listeners — see
`/run/hive/priv.sock` for privileged ops). the *Control plane (no network)* bullet under [Network
These are bind-mounted into containers via the nspawn conf. UDS paths map](#network-map) above. `PRIVATE_NETWORK=1` has no effect on a path
traverse the VFS, not the network stack, so `PRIVATE_NETWORK=1` does not that never touches the network stack.
affect them.
The nix side also enables IP forwarding + NAT (agents reach the internet The nix side also enables IP forwarding + NAT (agents reach the internet
through the host) and drops bridge-subnet → loopback traffic (defence-in-depth through the host) and drops bridge-subnet → loopback traffic (defence-in-depth