The Paranoia of Packets (Log 1: The Network)
Outside, across the spectral waste of the grand unwashed WAN, the bots crawl like irradiated cockroaches. They sniff at ports, rattle digital doorknobs, and send a cacophony of SYN packets screaming into the void. You do not want them in here.
You want the silence.
You want the Sovereign AI Lab, but sovereignty is a paradox—to rule, you must first build the walls, yet to govern, you must maintain the lines of supply. We are not building a network; we are constructing a filter against the entropy of the open web. And because true security demands obscurity, we do not publish our maps. We publish only the architecture of the maze.
The Double-Blind Shell Game
Consider the topology not as a tree, but as a series of airlocks. The traffic arrives from the ISP, wet and chaotic, hitting the Primary Router. It is a pedestrian device, a decoy. The traffic thinks it has found home. It hasn’t.
It flows downstream to the Secondary Router, the second layer of the onion, the bureaucratic obfuscation where the real work begins. This is the Double NAT—a geometric frustration for the uninvited. But sitting there, humming in the rack, is the Bastion. It is the gatekeeper. It is the three-faced Janus.
The Bastion: Maxwell’s Demon in Rocky Linux
The Bastion is not merely a server; it is a checkpoint Charlie for packets. It possesses three distinct nervous systems, three interfaces wired into the kernel’s cortex:
The External Face: Staring into the WAN, taking the brunt of the noise from the upstream network.
The Internal Face: The gateway to the Sanctum, the Compute Zone.
The Ghost Face: The WireGuard interface. The wormhole.
This Bastion runs , a piece of software acting as the adjudicator of truth. It implements a ruthless logic: nothing enters the Compute Zone without a visa.
The Compute Zone: Where the GPUs Dream
Deep inside a private, unrouted subnet lie the heavy irons—the DGX Spark nodes and the Kubernetes Control Plane. This is the Secure Compute Zone.
Here, the air is still. The silence is absolute. These machines cannot see the internet. If a node tries to ping Google, the packet hits the Bastion and dies, rejected by a rich rule in the firewall configuration. It is a digital Faraday cage.
But the machines must eat. They need updates, Python wheels, Docker layers. Enter Squid, the transparent proxy.
The Bastion runs Squid on a local port. It intercepts HTTP/HTTPS traffic from the Compute Zone. It inspects the destination. Is it ? Is it ? If the destination is on the whitelist, the packet is blessed and sent forth. If it is some unknown telemetry endpoint trying to phone home, it is dissolved into nothingness.
The WireGuard Wormhole
How do you, the architect, enter this hermetically sealed tomb? You do not open a door. You fold space.
We use WireGuard on a specific UDP port, a protocol of elegant, cryptographic silence. Unlike the chatty VPNs of old that announce their presence with elaborate handshakes, WireGuard stays silent until it sees a key it recognizes.
The path is circuitous, a Rube Goldberg mechanism of routing:
Your client, drifting somewhere on the 4G cellular ether, sends a packet to the public endpoint. The Primary Router catches it, sees the UDP tag, and flings it to the Bastion’s dedicated backchannel interface, separate from the primary wired WAN.
The key turns. The tunnel opens. Suddenly, you are bilocated. Your physical body is in a coffee shop; your digital soul is inside the Compute Zone, SSH-ing into the DGX Spark as if you were sitting on the rack.
We have built a fortress. The GPUs are safe. The data is sovereign. The silence is ours.
Next: Now that the walls are up, we must fill the void. In Part 2, we descend into the Setup, where we will attempt to birth a Kubernetes cluster inside this vacuum—and discover the agony of the whitelist.