Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.xloud.tech/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Every project in Xloud Networking starts with a network — an isolated Layer 2 broadcast domain that instances attach to via virtual ports. Paired with a subnet, it defines the IP address space, DHCP assignment, and routing gateway for your workload tier.
Prerequisites
  • An active Xloud account with appropriate permissions
  • Access to the Xloud Dashboard or CLI configured with credentials
  • API credentials sourced (source openrc.sh)

Create a Network and Subnet

1

Navigate to Networks

Navigate to Network > Networks in the sidebar. Click Create Network.
2

Configure the network

The create dialog shows the following fields:
FieldTypeRequiredDescription
Network NameTextYesNetwork display name
DescriptionText areaNoOptional notes
Available ZoneDropdownNoPin to a specific zone
MTUNumberNoMaximum transmission unit (68-9000, default: 1500)
Create SubnetCheckboxNoToggle to create a subnet with the network
Port Security EnabledSwitchNoEnable/disable port security (default: enabled)
Administrators see additional fields: Shared (make visible to all projects), External Network (mark as router external gateway), Project selector, and Provider Network Type (vxlan, flat, vlan, gre) with segmentation ID.
3

Configure the subnet (if enabled)

When Create Subnet is checked, additional fields appear:
FieldTypeRequiredDescription
Subnet NameTextYesSubnet display name
IP VersionDropdownYesIPv4 or IPv6
CIDRTextYesNetwork address block (e.g., 192.168.10.0/24)
For IPv6, additional fields appear: RA Mode and Address Mode with options dhcpv6-stateful, dhcpv6-stateless, slaac.Advanced options (click to expand):
FieldTypeDescription
Disable GatewayCheckboxRemove the default gateway from the subnet
Gateway IPIP inputCustom gateway address (auto-assigned if blank)
Enable DHCPRadioEnable or disable DHCP for this subnet
Allocation PoolsText areaIP range pairs (e.g., 192.168.10.2,192.168.10.200)
DNSText areaOne DNS server per line
Host RoutesText areaStatic routes (e.g., 192.168.200.0/24,10.56.1.254)
Choose a CIDR that does not overlap with existing subnets in your project. Overlapping subnets cause routing failures that are difficult to diagnose.
4

Create the network

Click Confirm. The network appears in the list with status Active.
Network shows status Active with the configured subnet.

View Networks

Navigate to Network > Networks. The list shows networks in tabs:
TabShows
Current Project NetworksNetworks owned by your current project
Shared NetworksNetworks shared across projects
External NetworksNetworks with external gateway capability
All NetworksAll visible networks (admin role required)
List columns:
ColumnDescription
ID/NameNetwork identifier (clickable to view details)
Is Current ProjectWhether the network belongs to your project
ExternalWhether this is an external gateway network (Yes/No)
SharedWhether the network is shared across projects (Yes/No)
StatusActive, Build, Down, or Error
Subnet CountNumber of subnets (with popover showing details)
Created AtCreation timestamp
Filter by Name, Shared, External, or Project Range.

Network Detail

Click a network name to open the detail page. Three tabs are available:
  • Detail — Network configuration summary
  • Subnets — All subnets in this network with CIDR, DHCP status, gateway
  • Ports — All ports attached to this network (instances, routers, DHCP)

Next Steps

Subnets

Add additional subnets to your network for multi-tier isolation

Routers

Connect your network to the external internet with an L3 router

Security Groups

Define firewall rules to control traffic to your instances

Floating IPs

Allocate public IPs and associate them with your instances