Skip to content
darklabs9

Network & Operational Security

Keep the house apart from the blast radius

A UniFi Dream Machine sits between the internet and everything at home. Two links, six zones, no open ports for web apps, and a teaching style that starts with whatever someone already owns.

Map

How the network is shaped

Conceptual only. No addresses, no VLAN numbers. If a box fails, traffic should have somewhere else to go, and devices that do not need to talk should not be able to.

Network tree: two internet connections feed a gateway and firewall with automatic failover. Cloudflare Tunnel and Access form the public edge, and Tailscale provides our remote access, both reaching in through the gateway. From the gateway traffic splits into six zones: Trusted, Guest, Surveillance, IoT, Storage, and Homelab. Homelab feeds services, then backups, then an off-site copy. Monitoring watches the lab. No addresses or VLAN numbers are shown.

Segmentation

Left hand, right hand

Segmentation means putting different kinds of devices on separate lanes (VLANs) on the same physical network. Each zone only talks to what it needs.

Picture your hands. Right hand: cameras and sensors. Left hand: your computer and family phones. Keep them apart. If a cheap camera gets weird, it should not be sitting next to the laptop that holds tax docs and school files.

Trusted

Personal laptops and phones.

Guest

Visitors get internet, not your stuff.

Surveillance

Cameras, on their own recorder.

IoT

Smart plugs, TVs, sensors.

Storage

NAS and backup targets.

Homelab

Servers and the services they run.

Failover

Two internet connections

If one link drops, traffic moves to the other automatically. The gateway handles that handoff so the house does not wait on someone noticing the outage first.

Public edge

How public things are exposed safely

The default is closed. Anything public has to earn its path out, and sensitive admin tools get an extra gate.

No open inbound ports

Web apps do not sit on the public internet waiting for whoever knocks.

Cloudflare Tunnel

Public sites go out through a tunnel. The house reaches out; strangers do not reach in.

Access gate

Sensitive admin apps sit behind Cloudflare Access with an email one-time code allowlist.

WAF and rate limits

Public tools get WAF rules, bot checks, and rate limits so abuse is harder by default.

Remote access

How we get in from elsewhere

Tailscale is a private mesh VPN. A subnet router into the lab lets us reach what we need without punching holes in the firewall. Outbound privacy VPN (Proton VPN) is available when we want traffic to leave that way.

On the security side: Elastic Fleet agents on key servers, Wazuh for security monitoring, and automated code review that blocks committed secrets.

Teaching story

Start where they already are

I told a coworker about my setup and overwhelmed her. “That’s a lot, I don’t really understand.” Fair. I switched.

I asked what she had at home. She showed her Ring cameras and a standard ISP router. No lab tour. Just her gear.

Analogy: left hand and right hand. Right hand is cameras and sensors. Left hand is your computer and family phones. Keep them apart so a compromised camera is not sitting next to the laptop that holds your life.

I said go home, open the router app, play with it, and send me screenshots and questions. We walked through it together and moved her cameras to the guest network, with main devices on the main network. Afterward she could explain why segmentation matters and manage the split herself.

How I teach

Principles that survive real houses

DNS at home is handled by the gateway with split-horizon DNS (inside names resolve locally; outside goes through Cloudflare). A self-hosted DNS server is staged for later. None of that is the first lesson for a friend with a Ring camera and an ISP router.

Start with what they already have

Their router, cameras, and phones set the first lesson. My lab is optional context, not the syllabus.

Curiosity sets the depth

I run something like a small Google Cloud at my house. You do not need that. What do you run?

Use a picture they can hold

Left hand / right hand beats a VLAN lecture. Keep cameras and personal devices apart, then explain why.

Let them drive

Screenshots, questions, and their own router app. The goal is that they can manage the split without me.

Verify the setting, not the label

Guest Wi-Fi is only isolation if guest isolation actually works. Check it. Then trust it.

Teach the why

If they can explain why segmentation matters, the setup survives the next ISP app redesign.

Want the short guides, or want help?

Plain-language lessons on /learn, or send a note if you want a hand separating your own network.