Networks and subnets in xneelo Cloud

In xneelo Cloud, a network is a virtual network that provides connectivity between cloud resources like instances, storage, and applications within your project.

In xneelo Cloud, there are two types of networks:

• Public networks:
  • Provide internet access
  • Pre-provisioned by xneelo
  • Available to all customers
• Private networks:
  • Keep network traffic isolated within your project
  • Created and managed by you
  • Only accessible to your own cloud resources

You can connect multiple networks together using a router.

Instances can have interfaces (ports) attached to multiple networks, either public or private.

A subnet is a range of IP addresses within a network. It provides addresses for connected resources and defines a gateway IP for routing. 

You can create and configure subnets to segment traffic or support different applications.

• CIDR (Classless Inter-Domain Routing) defines the IP range (e.g., 10.0.0.0/24)
• Gateway IP routes traffic out of the subnet
• DHCP can automatically assign IP addresses to your instances
• DNS servers and host routes can be set per subnet for custom configurations

This allows you to create a private network and subnet. The network defines the connection, while the subnet provides IP addresses for your instances.

The subnet gateway you can leave default, change, or disable.

To use a private network, your instance must be attached to it through an interface or port.

Create the network:

1. 1
   In the Cloud dashboard, go to Network > Networks.
2. 2
   Select the Create Network button.
3. 3
   Enter a name for the network.
4. 4
   Leave Enable Admin State and Create Subnet checked.

Create the subnet:

1. 1
   Select the Subnet tab (or Next button).
2. 2
   Enter a name for the subnet.
3. 3
   Enter the Network Address (CIDR range).
4. 4
   Choose the IP Version: IPv4 or IPv6.
5. 5
   Set the Gateway IP either:

• Leave blank to use the default gateway (first IP of the subnet)
• Enter a custom gateway IP (must be inside the subnet range)
• Or select Disable Gateway to disable

Set additional subnet details (optional):

1. 6
   Select the Subnet Details tab (or Next button).
2. 7
   Enable DHCP to automatically assign IPs.
3. 8
   Define Allocation Pools (IP ranges for DHCP).
4. 9
   Add custom DNS Servers.
5. 10
   Add Host Routes for advanced setups.
6. 11
   Select Create to finish.

Your network and subnet will now appear in the Networks list.

Once the network is created, you can proceed to manage the network ports.

After creating a private network and subnet, you can connect it to other resources in your project.

Connect to an instance:

• This allows the instance to communicate on a private network
• This involves attaching an interface (vNIC) to the instance and connecting it to the private network
• Follow the steps to attach an interface to an instance

Connect to a router: 

• This allows traffic to move between networks, or out to the internet (if the router is connected to an external gateway)
• This involves creating a router interface and connecting it to the private network
• Follow the steps to connect a router to a private subnet

You can create additional subnets on the same network if you need more IP ranges or want to separate traffic.

Each subnet must have a unique CIDR range that doesn’t overlap with other networks in your project.

STEPS

1. 1
   On the Networks page, find the network you want to update.
2. 2
   In the Actions column, select the down ▼ button and Create Subnet.
3. 3
   Enter a name for the subnet.
4. 4
   Enter the Network Address (CIDR range).
5. 5
   Choose the IP Version: IPv4 or IPv6.
6. 6
   Set the Gateway IP either:

• Leave this blank if you want to use the default gateway value (the first IP of the network address).
• Set a custom IP address of the gateway.

1. 7
   Select the Disable Gateway toggle if you want to disable the gateway.

Set additional subnet details (optional):

1. 8
   Select the Subnet Details tab (or Next button).
2. 9
   Enable DHCP to automatically assign IPs.
3. 10
   Define Allocation Pools (IP ranges for DHCP).
4. 11
   Add custom DNS Servers.
5. 12
   Add Host Routes for advanced setups.
6. 13
   Select Create to finish.

Once the subnet is created you can proceed to manage the network ports.

You can edit subnet settings such as allocation pools, DNS servers, or host routes.

STEPS

1. 1
   On the Networks page, find the network you want to edit.
2. 2
   Select the Network Name (blue hyperlink), then the Subnets tab.
3. 3
   Find the subnet you want to edit.
4. 4
   In the Actions column, select Edit Subnet.
5. 5
   Update the settings as required.
6. 6
   Select Save.

If you no longer need a network or subnet, you can delete it.

Note: Before a network or subnet can be deleted, you must first remove any dependencies. See how to delete the router, and then remove all associated interfaces (ports).

Delete network:

1. 1
   On the Networks page, find the network you want to remove.
2. 2
   Select the Network Name (blue hyperlink), then the Ports tab.
3. 3
   Select all the ports listed on the network.
4. 4
   Select the Delete Ports button.
5. 5
   Go back to the Networks page.
6. 6
   In the Actions column, select the down ▼ button and Delete Network.
7. 7
   Select Delete Network to confirm.

Delete subnet:

1. 1
   On the Networks page, find the network you want to remove.
2. 2
   Select the Network Name (blue hyperlink), then the Ports tab.
3. 3
   Select the ports associated with the subnet.
4. 4
   Select the Delete Ports button.
5. 5
   Select the Subnets tab.
6. 6
   Find the subnet you want to remove.
7. 7
   In the Actions column, select the down ▼ button and Delete Subnet.

A network port is a virtual connection point that links a device (such as an instance or a router) to a network. Each port has its own IP address and security groups.

Learn how to manage network ports in xneelo Cloud.

If your instances cannot connect on a private network, check the following:

• The instances are attached to the correct network
• The subnet CIDR ranges do not overlap with other networks in your project
• The gateway IP is valid and within the subnet range
• DHCP is enabled if you want instances to receive IP addresses automatically
• If DHCP is disabled, ensure the instance has a valid static IP configuration inside the operating system
• DNS servers are configured if you need name resolution on the network
• Any host routes are configured correctly, if used
• The security groups on the instance or port allow the required traffic
• Any firewall rules inside the operating system allow the required traffic

If you are using a router, also check the following:

• The private subnet is connected to the correct router
• The router interface was added successfully
• The router has an external gateway configured, if internet access is required
• The correct routes are in place between connected networks

Tip: If the network and subnet appear correct in the Cloud dashboard, but the instance still cannot communicate, check whether the operating system interface is configured correctly and has an IP address assigned.

For more help, see interfaces on cloud instances and routers in xneelo Cloud.