A private network (VPC) gives your servers an isolated network they talk over using internal IPs, with nothing exposed to the public internet. Add routes on top and you control where traffic for any destination goes: through a firewall VPS, a NAT Gateway, or an appliance you run yourself.

It's the building block for multi-tier applications (web in front, database on a private subnet), private clusters, NAT egress, and anything where servers should reach each other without public IPs.

Create a network

  1. 1
    Open the create flow
    On the Private Networks page in my.cubepath.com, click Create Network.
  2. 2
    Set name, location and range
    Enter a name (3–64 characters), choose a location, and set the IP range as a CIDR, e.g. 10.0.0.0/24.
  3. 3
    Create
    Confirm. The network is regional: only machines in the same location and project can join.

Rules for the range

RuleDetail
PrefixBetween /8 and /24
RangeMust sit entirely inside a private range, 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16. Any other range is refused
AddressMust be the true network address for the prefix. 10.0.0.0 is valid for a /24, 10.0.0.5 is not
Reserved.0 (network), .1 (gateway), the broadcast address and the two addresses just below it (.253 and .254 in a /24), which the gateway itself uses. Everything else is assignable
LimitUp to 3 networks per organization

Attach servers

Open a machine's Network tab (VPS or baremetal) and Attach it. The server takes the next free internal IP from the range.

  • The server must be in the same project and location as the network, and be active or stopped.
  • A VPS must be restarted for the change to take effect. Baremetal applies the switch configuration in the background, but you still have to configure the VLAN inside the OS.

Routes

By default a network only knows how to reach its own CIDR. A route tells it to send traffic for some other destination through a next hop you choose. Add one from the network's Routes tab with Add route.

FieldMeaning
Destination CIDRThe target CIDR, e.g. 0.0.0.0/0 (everything) or 192.168.50.0/24
Target typeWhat the next hop is: an IP, a VPS, or a baremetal server
Gateway IP / Target resourceThe next hop itself: an address inside the network (for an IP), or the server (for a VPS or baremetal)

Typical uses: send all outbound traffic through a firewall VPS, or route a remote subnet through an appliance's internal address.

What's allowed

  • The destination can't be the network's own CIDR (that's already connected) and can't sit in a reserved range (0.0.0.0/8, loopback, link-local, multicast, 240.0.0.0/4) or inside CubePath's own public address space. A supernet like 0.0.0.0/0 is fine. A destination with host bits set is saved as its network address (10.1.2.3/24 becomes 10.1.2.0/24).
  • An IP next hop must be inside the network's CIDR, and can't be .0, .1, the broadcast address or the two addresses just below it.
  • A server next hop must be in the same project and already attached to this network, otherwise it's unreachable and the route is rejected.
  • Routes are IPv4 only. An IPv6 destination or next hop is refused.
  • Up to 30 routes per network. The same destination can have more than one next hop (treated as equal-cost paths); only an exact duplicate is refused.

What it doesn't do

  • It isn't a public network. Private IPs are reachable only by your attached servers in the same location. For outbound internet from a private-only server, route through a NAT Gateway.
  • It doesn't span locations. A network lives in one location. Connect locations with a routing appliance and routes.

Troubleshooting

SymptomLikely cause
"Invalid range" on createThe range isn't the network address for that prefix
"Must be private" on createThe range is outside 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16
"Limit reached" on createYou already have 3 networks
Can't attach a serverIt's in another project or location, or it isn't active/stopped
Attached but no connectivityOne or both VPS haven't been restarted since attaching
Route rejected, next hop outside CIDR or reserved for the gatewayAn IP next hop must be an address within the network, and not .0, .1, the broadcast or the two addresses just below it
Route rejected, reserved range or CubePath's address spaceThe destination is a reserved range or part of CubePath's own public addresses
Route rejected, "must be attached"The target server isn't on this network yet
Can't delete the networkA VPS, baremetal server or NAT Gateway is still attached