Skip to main content

VPC Networking

Overview​

  • What VPC provides (isolated L2 overlay networks per tenant using VXLAN)
  • Key capabilities: private subnets, NAT gateways, multi-hypervisor spanning

Prerequisites​

  • Physical/hardware requirements:
    • Secondary NIC on each hypervisor connected to a shared VLAN/switch
    • All hypervisors in the group on the same L2 segment (same VLAN)
    • This interface carries VXLAN-encapsulated traffic (UDP 4789, multicast 239.1.1.1)

Admin Configuration​

Step 1: Navigate to Hypervisor Groups​

  • Admin Panel → Compute → Hypervisor Groups → Edit group

Step 2: Enable VPC​

  • Toggle "Enable VPC" on
  • Configure VXLAN range (default 10000–16777214)
  • Set L2 Interface name (the secondary NIC, e.g., eth1, ens192)
  • System auto-assigns 169.254.x.x link-local IPs to each hypervisor
  • Visible in hypervisor table when VPC is enabled
  • Used for inter-hypervisor VXLAN control plane

Step 4: Configure NAT Gateway (Optional)​

  • Enable NAT Gateway toggle (optional)
  • Set pricing: monthly credit value, bandwidth rate per GB (optional)
  • Configure bandwidth accounting mode (uploads/downloads/both)
  • Configure overage policy (no limit / charge overage / revoke access)
  • Set IPv4 monthly credit value ( This is the IPv4 assigned to the NAT gateway )

User Guide​

Creating a VPC​

  • Dashboard -> Networking → VPC → Create VPC
  • Name, description, CIDR (10.0.0.0/16, 172.16.0.0/16, or 192.168.0.0/16)
  • Select Location (must have VPC enabled)

Creating Subnets​

  • Inside VPC → Create Subnet
  • Subnet CIDR within VPC range (e.g., 10.0.1.0/24)
  • Gateway auto-assigned (first usable IP)
  • IPs auto-generated for the range

Deploying Instances​

  • Create instance → select VPC and subnet
  • Instance gets a VPC interface with private IP from subnet
  • Cloud-init configures networking automatically
  • Multiple instances in same subnet can communicate directly

NAT Gateway​

  • Enable NAT gateway on VPC for outbound internet
  • System allocates a public IPv4 address
  • All instances in attached subnets get outbound connectivity via SNAT
  • Bandwidth metered per configuration