Skip to main content

Overview

The Network panel under Project → Network provides a complete interface for building and managing virtual network infrastructure. You can create isolated project networks, configure DHCP subnets, route to external networks, and assign floating IPs to instances.
Prerequisites
  • member role in the active project
  • At least one provider network configured by an administrator (for external routing and floating IPs)
  • Networking service enabled on your Xloud deployment

Network Topology View

Navigate to Project → Network → Network Topology for a visual diagram of all networks, routers, and instances in your project. The topology shows:
  • Networks as horizontal lanes
  • Instances as nodes connected to their networks
  • Routers connecting project networks to external networks
  • Floating IPs as labels on instances with external access
Click any element to view its details or perform actions directly from the diagram.

Create a Network

Open the Create Network wizard

Navigate to Project → Network → Networks and click Create Network.

Network tab

FieldDescription
Network NameDescriptive name (e.g., web-tier, db-private)
Enable Admin StateKeep enabled to activate the network
Create SubnetToggle on to add a subnet in the same step
Availability Zone HintsOptional AZ affinity for the network’s DHCP agents

Subnet tab

FieldDescription
Subnet Namee.g., web-subnet-01
Network AddressCIDR range (e.g., 10.10.1.0/24)
IP VersionIPv4 or IPv6
Gateway IPDefault gateway — leave blank to auto-assign (first IP in range)
Disable GatewayCheck to create an isolated network with no default route

Subnet Details tab

FieldDescription
Enable DHCPAuto-assign IPs to instances (recommended)
Allocation PoolsOverride DHCP pool range (e.g., 10.10.1.100,10.10.1.200)
DNS Name ServersOverride DNS servers pushed to instances via DHCP
Host RoutesStatic routes injected via DHCP (e.g., 192.168.10.0/24,10.10.1.1)

Create

Click Create to finalize. The network appears in the list with Active status and the subnet is listed under Project → Network → Subnets.
The network is now available in the Networks tab when launching instances.

Create a Router

Routers provide Layer 3 routing between project networks and to external (provider) networks for internet/floating IP access.

Create the router

Navigate to Project → Network → Routers and click Create Router.
FieldDescription
Router Namee.g., main-router
Enable Admin StateKeep enabled
External NetworkSelect the provider network for external access (e.g., public, external)
Enable SNATEnable Source NAT for outbound traffic from private instances

Add interfaces

After creation, click the router name and navigate to the Interfaces tab. Click Add Interface.Select the subnet to connect (e.g., web-subnet-01). Leave IP Address blank to use the subnet gateway. Click Submit.Repeat for each subnet the router should serve.
Instances on the connected subnet can now route to the external network through the router.

Floating IPs

Floating IPs provide a stable public IP address that can be associated with an instance’s private IP, enabling inbound external connectivity.

Allocate a floating IP

Navigate to Project → Network → Floating IPs and click Allocate IP To Project.Select the Pool (external/provider network). Click Allocate IP.

Associate with an instance

In the floating IP row, click Associate. Select the instance and the instance’s port to bind. Click Associate.
The instance is now reachable from external networks at the floating IP address.

Security Groups

Security groups are stateful firewall rules applied at the port level.

Create a security group

Navigate to Project → Network → Security Groups and click Create Security Group. Enter a name (e.g., web-http) and description.

Add rules

Click Manage Rules on the new group. Click Add Rule:
FieldDescription
RuleProtocol shortcut (HTTP, HTTPS, SSH, Custom TCP, etc.)
DirectionIngress (inbound) or Egress (outbound)
Open PortSingle port or port range
RemoteCIDR (IP range) or another security group
Reference another security group as the Remote to allow traffic between all instances in that group — useful for tiered architectures (web → app → db).

Next Steps

Networking User Guide

Full networking documentation with advanced configurations

Manage Instances

Attach networks and security groups during instance launch

DNS Configuration

Configure DNS for instances and floating IPs

Load Balancer

Distribute traffic across multiple instances