Tag: networking

How to expose a possibly-vulnerable app to the public internet and survive it: rootless containers, a file-integrity tripwire, and zero inbound SSH on the box.

Ingress is the annotation-soup classic. Gateway API is the role-oriented future with proper L4/L7 separation. Here's when to migrate and when to wait.

Rootless Docker tuning deep-dive: network drivers, env vars, port drivers, cgroup delegation, and real troubleshooting — anchored to Docker Engine 29.x.

Boot any OS over the network using iPXE — covers dnsmasq proxyDHCP setup, HTTP boot menus, Talos OS live boot, and the quick netboot.xyz shortcut method.

Mikrotik routers cost $50, run a real OS, and humiliate prosumer gear. RouterOS basics, VLANs, firewalling, and why your homelab probably needs one of these.

Two FreeBSD firewall distros, one bitter fork. pfSense vs OPNsense in 2026 — which one to pick for your home lab, and why the licensing drama still matters.

Zeek (formerly Bro) turns network traffic into structured logs you can actually query. The IDS that doesn't shout — it documents. Setup and use in a home lab.

traceroute lies. mtr tells the truth. Here's how to read packet-loss reports like an oncall engineer and stop blaming your ISP for the wrong hop.

Your gigabit link drops to 200 Mbps and you don't know why. iperf3 measures throughput honestly, nload visualizes traffic — together they find the bottleneck fast.

Expose Docker's Unix socket over TCP so remote tools and dashboards can connect — daemon.json config for Linux and Windows.

Go beyond basic UFW rules — rate limiting, geo-blocking, application profiles, logging, and before.rules tricks for serious firewall hardening.

Network aliases give containers multiple DNS names. Perfect for blue-green deploys and service discovery patterns.