Not Just a Stack of VMs: VyOS Plays Here Also

As part of the CodexMCP project, this setup isn’t just about automating VM deployments—it’s about creating a fully routed, isolated network that operates like a real ISP backbone. The goal is to move beyond basic infrastructure automation and into network engineering as code, allowing for real-world testing, dynamic service deployment, and future scalability.

How This Network is Structured

• VyOS Core Routing – A VyOS router sits at the center, dynamically handling internal routing across multiple subnets. This isn’t a flat, single-network setup—it’s a properly segmented environment with real traffic flow.
• Isolated 10.x.x.x Network – The entire system runs on a dedicated 10.x.x.x space, completely isolated from my main network. This ensures a controlled, ISP-like deployment where services operate independently.
• Proxmox Bridges as Virtual Switches – Instead of using external hardware, Proxmox bridge interfaces act as virtual switches, connecting VMs across different network segments in a flexible and modular way.
• ISP Simulation with a Dedicated Edge Router – Beyond the core network, a second ISP-facing router connects to the core and manages simulated customer traffic. This means:
  • Services like DHCP, DNS, and RADIUS operate just as they would in a production ISP environment.
  • Network traffic is routed properly between infrastructure layers, rather than just living inside a Proxmox node.
  • This setup allows for testing real provisioning workflows, automation, and troubleshooting in a controlled environment.

What’s Next? Expanding Beyond Virtualization

A future phase of this project will extend beyond Proxmox and VyOS routing by incorporating physical networking hardware:

• A Brocade switch will be added, providing real switching functionality for VoIP phones and additional hardware integrations.
• This switch will also connect to a second Proxmox cluster in another room, simulating a multi-ISP environment where two independent ISPs interact.
• The goal is to test cross-site routing, real-world VoIP infrastructure, and more advanced ISP service deployments within CodexMCP.

Why This Approach?

Building the network this way allows for deeper testing and refinement of ISP automation strategies, service orchestration, and troubleshooting workflows. This isn’t just about running virtual machines—it’s about simulating an entire operational network.

And the best part?
Right now, this entire network deploys from scratch in ~15 minutes.
(Exact numbers coming soon.)

This is just the beginning.

-Hack The Planet
--Bryan Vest