Network engineering · Cibolo, Texas
I learned networking by breaking it and fixing it. Now I run a district network and write the explanations I wish I'd had — from first principles to the protocol-level details.
Expertise
End-to-end design and deployment of district-wide networks. Rebuilt subnets from the ground up, standardized rack layouts, deployed the full UniFi stack from core switching to edge access points, and wrote the firewall policy that holds it together.
Keeping the core running: Active Directory on Windows Server, Linux for localized tooling, Proxmox for bare-metal virtualization, and Google Workspace for the identities everything authenticates against.
Vendor selection and rollout of everything a person touches: Yealink VoIP, Elevate Sky print management, and district-wide desktop, laptop, and tablet fleets measured in thousands of devices.
Start here
One keystroke, four protocols, and about 200 milliseconds. A walk through the exact sequence a browser performs before it can render a single pixel.
6 min read
Subnetting is arithmetic, not trivia. Learn the four numbers every address carries and you can size a network without a calculator.
4 min read
How a single 48-port switch keeps students, staff, and cameras in separate broadcast domains, and why that separation is convenience rather than security.
5 min read
Series
Each series builds a ladder. Beginner pieces assume nothing; advanced pieces assume the ones before them.
The stack explained without hand-waving. Start here if a VLAN is still an abstraction.
What a switch actually does with a frame, and why loops, uplinks, and power budgets decide whether the campus stays up.
From channels and airtime to OFDMA, BSS coloring, and multi-link operation.
Trust boundaries, stateful filtering, 802.1X, and what inspection really costs.
Documentation, read-only auditing, change windows, and the multicast problem nobody warns you about.
From the routing table to a second campus: static routes, summarization, site links, and the failure modes that come with them.
Reading a capture instead of guessing. tcpdump, Wireshark, and the five patterns that explain most tickets.
The two services every other service assumes, at the depth a production network needs.
Zones, state, NAT, and the discipline of a rulebase you can defend in an audit.
IPsec, WireGuard, TLS tunnels, and where zero trust actually replaces a VPN.
Circuits, BGP at the edge, SD-WAN claims versus reality, and QoS where the bill is.
Everything you need to know what the network is doing, from SNMP to alert design.
Copper, fiber, testing, and the rack standards that make everything above them maintainable.
Classification, queuing, and why voice breaks at 07:55 while everything else looks fine.
NETCONF, RESTCONF, YANG, and Python that changes a network safely.
The controller, end to end: adoption, VLANs, zones, Wi-Fi, switching, and the settings that bite.