Support Engineer // Homelab Builder // Cybersecurity Practitioner
Always Tinkering /// Always Learning /// Always Evolving ∞
Open to Remote
Available
I build things, break them, figure out why, and document everything. My homelab (tomlab.space) runs a Proxmox hypervisor, two production VMs, and a Docker stack of 15+ containers including a self-hosted DNS cluster, Caddy reverse proxy with automatic TLS, and Tailscale across all nodes as the critical out-of-band access layer.
When network changes go wrong and I lose LAN connectivity, Tailscale is how I get back in. I've debugged its MagicDNS behavior in production, hardened SSH around it, and built it into my infrastructure recovery procedures. That kind of hands-on problem-solving is where most of my real networking knowledge lives.
10+ years of customer-facing technical experience across Apple, Micro Center, and independent IT work — explaining complex systems clearly to people under pressure is the core of what I do. Right now I'm working toward support engineering and cybersecurity: daily HackTheBox and TryHackMe labs, Cisco Ethical Hacker in progress, building toward CEH and the TryHackMe SAL1 and PT1 paths.
dashed border = active study / in-progress deployment
Production homelab running Proxmox VE with two VMs (Docker stack and DNS), 15+ Docker containers, VirtioFS storage passthrough, and full service documentation. Everything built, broken, fixed, and documented.
Tailscale mesh VPN deployed across Proxmox host and Docker VM as the critical out-of-band access layer. SSH restricted to LAN subnet + Tailscale subnet only. Debugged MagicDNS conflict (accept-dns=false + chattr +i on resolv.conf). Survived multiple network recovery scenarios.
Redundant DNS/DHCP cluster across Raspberry Pi 3B+ (primary, 192.168.86.2) and Debian VM (secondary, 192.168.86.3). DNS sinkhole, DHCP reservations, custom local records. resolv.conf locked with chattr +i on all hosts.
Caddy serving as the reverse proxy for all internal services with automatic TLS via ACME/Let's Encrypt. Security headers, scanner blocks, and per-service routing configured. External domains routed through Cloudflare DNS.
Custom-built internal homelab dashboard featuring live NVD CVE monitoring, OWASP audit status, RSS threat intel feeds, network topology viewer, and BOM tracker. Hand-coded HTML/CSS/JS, served via Caddy.
Full infrastructure security audit with documented findings and remediation. Resolved 10+ incidents: USB NIC autosuspend, fstab UUID instability, Docker disk exhaustion, Tailscale DNS hijacking, SMB permission failures, NVIDIA phantom services, non-root SSH hardening.
5-VLAN design in progress: Management (10), Services (20), Downloads (30), Trusted (40), IoT (50). OPNsense planned on dedicated Intel node post-migration to AM4 server hardware. Managed rackmount switch already 802.1Q capable. Canvas diagram built in Obsidian.
I'm actively looking for support engineering and infrastructure roles. Remote preferred. If you're building something interesting — especially in networking or zero-trust access — I want to hear about it.