skip to content
eric @ arcrayde

eric@arcrayde: ~/portfolio

$ whoami

Eric Drake

$ cat bio.txt

AI Curious

$ ls ~/domains

  • network automation
  • routing & switching
  • packet analysis
  • source of truth
01 $ cat about.md

About

I work on the parts of a network that decide whether everything else behaves: how routes are chosen, how traffic is segmented and carried, and where the authoritative record of it all actually lives.

Most network problems I care about are really data problems. A single source of truth turns a network from a collection of device configs into something you can query, validate and automate against — so changes stop being folklore and start being reproducible.

When something breaks, I'd rather read the packets than guess. Capture first, form a theory second — Wireshark has settled more arguments than any diagram.

Lately I'm AI curious: poking at where models are genuinely useful in network operations, and where they are just an expensive way to be confidently wrong.

profile.yaml

focus:
network infrastructure & automation
layers:
L2 / L3 — switching, routing, transport
exploring:
AI applied to network operations
contact:
drakes2005@protonmail.com
02 $ show capabilities

Skills

capabilities.tbl

10 entries

  • 01 Network Single Source of Truth data
  • 02 Network Automation automation
  • 03 Routing / Switching core
  • 04 Virtual Network Functions virtualization
  • 05 Packet Capture analysis
  • 06 Wireshark Analysis analysis
  • 07 VPN security
  • 08 BGP routing
  • 09 OSPF routing
  • 10 MPLS transport
03 $ ls -la ~/work

Projects

01

source-of-truth/

Network Source of Truth

Making the network queryable. One authoritative record of sites, devices, addressing and circuits — so intent lives in data rather than in a device config someone edited at 2am, and every downstream tool reads from the same place.

  • single source of truth
  • data modelling
02

automation/

Automation & Config Pipelines

Driving configuration from that record instead of by hand. Templated generation, pre-change validation and repeatable rollout, so a change is reviewable before it touches production and reproducible after it does.

  • network automation
  • validation
03

routing/

Routing, Switching & Transport

The control plane end of the job: BGP policy and path selection, OSPF areas and convergence behavior, MPLS transport underneath, and the L2 design that has to stay boring for any of it to work.

  • BGP
  • OSPF
  • MPLS
  • routing / switching
04

packet-analysis/

Packet Capture & Analysis

Evidence over intuition. Capturing at the right point in the path and reading what actually happened on the wire — handshakes, retransmits, MTU and timing — to separate the real fault from the convincing story about it.

  • packet capture
  • Wireshark
05

vnf/

Virtual Network Functions

Network functions as software: routers, firewalls and gateways running virtualised, which makes lab topologies disposable and lets a design be tested before it is bought.

  • VNF
  • virtualization
06

secure-connectivity/

Secure Connectivity

Getting traffic between sites and users without trusting the path in between — tunnel design, routing over the overlay, and keeping the failure modes understood rather than discovered.

  • VPN
  • tunnelling
04 $ ./contact.sh

Contact

Open to conversations about network infrastructure, automation, and where AI actually earns its place in operations. The inbox is the fastest route.

connect