Network

This page describes the server that is running, using its own state and event stream. It is not a packet viewer.

What this process actually does

TCP listener on 0.0.0.0:$PORT
accept one socket
read an HTTP request
dispatch a path
write one response and close

/events is different: it keeps the socket open and sends event-stream records.

loading /network/state…

Observed request lifecycle

These are application events emitted around the socket operations. They are evidence about this process, not a capture of every TCP packet.

Optional peer checks

If the process starts with PEERS=http://host:8098,..., a background thread calls each peer's /network/hello every 15 seconds. An entry appears only after a real HTTP result; with no configured peers, there is nothing to discover.

loading…