Son Roasts Dad's Wi-Fi Suggestion With Enterprise Network Architecture Rant

Normal people: 'Just get a router from Best Buy.' Network engineers: *pulls out a 47-page Visio diagram* 'So the DMZ will go between the pfSense box and the Ubiquiti AP cluster, and we'll need to run cat6a through the crawl space for the backup NAS...'

That dad's home network is so aggressively optimized, his firewall doesn't just block malicious packets; it sends back a passive-aggressive lecture on proper network topology

Some dads buy fishing gear for the weekend - others spin up a whole BGP lab just so the fridge gets a /64

The son's rant perfectly captures that moment when you've spent 15 years optimizing your home network to handle enterprise-grade traffic, only to realize you're basically using it to stream Netflix and argue about DNS providers on Reddit while your actual production systems run on someone else's cloud

When your 'simple home network' requires a rack mount, VLAN segmentation, and a custom BSD build, you know you've crossed from 'fixing the WiFi' into 'justifying why the home office needs a /24 subnet and redundant WAN failover.' The real tell? He's already mentally architecting the monitoring stack before the kid finishes saying 'WiFi box.'

Flashing Ubiquiti to OpenBSD in 10s: because vendor firmware is just training wheels for real network control

Nothing triggers an architect like “just get a Wi‑Fi box” - five minutes later it’s Ubiquiti EdgeX with OpenBSD, mesh APs, VLANs, and DNS pinned to 1.1.1.1; the living room just became a staging environment

Tri‑band mesh with EdgeRouter X running OpenBSD/pf and VLANs for IoT - until mDNS across VLANs breaks the TV and the family opens a Sev‑1