Network Infrastructure
This section documents the network architecture supporting the lab.
The design prioritizes latency consistency, operational simplicity, and predictable behavior under load over raw throughput or experimental features.
Network documentation focuses on intent, boundaries, and policy rather than exhaustive configuration listings.
Architecture Overview
The network follows a simple, hierarchical model:
- Single edge router providing routing, firewalling, and traffic policy
- Dedicated 10G core switching
- Access switching segmented by location and function
- Centralized VLAN termination (“router-on-a-stick”)
- Wireless provided by controller-based access points
Dynamic behavior is intentionally limited and tightly scoped.
The diagram below reflects logical topology and policy boundaries, not
physical rack layout or cabling paths.
┌──────────────────────────┐
│ Internet / WANs │
│ │
│ Spectrum 1G / 40M │
│ AT&T VDSL 100 / 20M │
└─────────────┬────────────┘
│
┌────────────▼────────────┐
│ MikroTik RB5009UG+S+ │
│ Edge Router │
│ │
│ - VLAN routing │
│ - Firewall │
│ - Dual-WAN CAKE (90%) │
│ - Policy steering │
└────────────┬────────────┘
│ 10G trunk (all VLANs)
┌──────────────────▼──────────────────┐
│ CRS317-1G-16S+ │
│ 10G Core Switch │
│ │
│ (pure L2, VLAN trunking) │
└───────┬──────────┬───────────────┬──┘
│ │ │
10G │ 10G │ 10G │
│ │ │
┌───────────────────▼┐ ┌─────▼─────────┐ ┌─▼─────────────┐
│ CRS326-24G-2S+ │ │ CRS309-1G-8S+ │ │ CRS310-8G+2S+ │
│ Rack Access Switch │ │ Office Switch │ │ Living Room │
│ │ │ │ │ Switch │
└────────┬───────────┘ └────────┬──────┘ └────────┬──────┘
│ 1G │ 2.5G │ 2.5G
┌────────▼────────┐ ┌──────▼──────┐ ┌─────▼──────┐
│ CRS112-8P-4S │ │ Ruckus R650 │ │ Ruckus R750│
│ PoE Access │ │ Office AP │ │ LivingRoom │
│ Switch │ │ (2.5G) │ │ AP (2.5G) │
└─────────────────┘ └─────────────┘ └────────────┘
┌──────────────────────────────────────────┐
│ Direct Core-Attached Servers │
│ │
│ • EPYC 7402P Proxmox Host │
│ - General compute │
│ - AI inference VM (dual RTX 3090) │
│ │
│ • TrueNAS EPYC Storage Server │
│ - Primary ZFS storage │
│ │
│ • Proxmox Backup Server (Xeon D-1518) │
│ - PBS datastore │
└──────────────────────────────────────────┘ Figure: Logical network topology. Servers attach directly to the 10G core; access and PoE switches do not provide upstream infrastructure services.
Documented Areas
- Edge & Traffic Policy
This document describes the authority boundaries at the network edge: where routing and policy decisions are made, where congestion is enforced, and what happens when an adaptive component fails.
- NetBox as Source of Truth
This document describes the role of NetBox as the authoritative source of truth for network design, addressing, and intent.
- Network Monitoring Intent
Network-specific visibility goals, evidence boundaries, and failure questions within the broader monitoring architecture.
- Switching & VLAN Fabric
This document describes the Layer 2 transport fabric and the boundaries it must preserve for routing, security, and QoS to remain inspectable.
- wanctl Control Plane
Adaptive CAKE control, external rate-controller integration, bounded WAN steering, and safety boundaries.
- Wireless
Authenticated Ruckus Unleashed cluster, radio, and WLAN policy evidence with explicit remaining failover and end-to-end verification gaps.