// WRITING / TAGS / NETWORKING
Networking is the layer that shows up in every incident postmortem and on no architecture diagram. It's the assumption everything else makes silently, and the failure mode everything else is downstream of. Most teams underinvest in it until they can't.
These posts are about what we've learned operating real networks. Address schemes that survive scaling. VLAN models that don't sprawl. The difference between switches that are configured and switches that are managed. The operational gap between "the network team" and "the platform team" that most organizations pretend doesn't exist.
Some of this is from the lab (Arista plus MikroTik, fully declarative, GitOps-managed). Some of it is from client environments where the network was the constraint nobody had named.
Network automation is harder than server automation because the blast radius of a mistake is immediate and the feedback loop is brutal. That brutality is actually the advantage. It forces you to get the abstractions right in a way that server automation lets you defer.
The thing that makes declarative automation powerful is exactly the thing that makes it dangerous. I wrote a user management task with handle_absent_entries: remove, defined a partial list, and RouterOS refused to execute because it would have deleted the last user with full access permissions. The safety net caught it. The lesson is about knowing where aggressive automation ends and self-inflicted disaster begins.
The 24-hour activation window is real. The support response time on a Friday night is real. The disk wipe if you miss the window is real. MikroTik is still the right choice. All of these things are true at the same time.
The destination was never in question. The uncertainty was entirely in the path: how Ansible, RouterOS, and a task sequence would negotiate the journey from current state to desired state on live hardware.
The on-site session was two and a half hours. Rack, cable, verify, leave. That wasn't luck. The bootstrap happened weeks earlier at a desk, not in the rack.
A home lab isn't a static thing. It grows through distinct phases. Wave one is making something work. Wave two is making it more complicated. Wave three is adding rigor. Wave four is building a true datacenter corollary. Most people stop at wave two. Wave four is where the interesting work is.
// RELATED TOPICS