Tag: networking
-
Side quest: the guest was reachable and its host was not
The first guest built on a chassis blade came up fine and answered on the network. The blade it ran on disappeared. No ping, no SSH, no management web interface, while the chassis still reported the blade as powered on.…
-
The kill switch that was only a comment
A container that downloads from the public internet was put behind a WireGuard sidecar so its traffic would leave through a VPN instead of the home connection. The design was chosen because it would fail closed: if the tunnel dropped,…
-
Side quest: the home lab for actually testing things
Most of what gets built for this project runs somewhere that other things already depend on. The chassis behind this new series is not that. It exists specifically so that breaking something costs nothing beyond a power cycle, and every…
-
Why Rathole
The services in this lab run on machines at home, behind a consumer internet connection. Some of them need to be reachable from the public internet. The home network has no ports open to the internet and no port forwarding…
-
Why Unbound
Every connection to anything starts with a name being turned into an address. In this lab that translation is done by two machines the lab owns, running Unbound, rather than by the internet provider’s resolver or by whatever the router…
-
Why Headscale
The machines in this lab are not all in the same place. Some are virtual machines at home, some are servers rented in other countries, and some are the devices people actually carry: laptops, phones and tablets, moving between home…
-
Status: first contact with real hardware
Two things happened that had not happened before. The standby gateway in Europe exists, which completes the pair at the edge. And a physical server was brought online for the first time, which ended the long stretch of this project…