Skip to main content
Last updated on

Network and Subnet

A Network is a virtual private network on LANIT Cloud — analogous to a VPC on other platforms. Each account can create several independent Networks to separate workloads (production, staging, internal, DMZ…). Inside a Network you create one or more Subnets — the specific IP ranges handed out to VMs.

Terminology​

ConceptMeaning
NetworkInternal virtual network, not routed directly to the Internet
SubnetA CIDR range inside a Network, handed out to VMs via DHCP or as a static IP
GatewayThe subnet's exit IP (usually the first or last address of the range)
DHCPAuto-assign IPs to VMs that attach to the subnet
Allocation PoolLimits the IP range that DHCP can hand out (reserves the rest for static IPs)

Create a Network​

Step 1. Open the Network page​

Go to Network → Networks and click + Create Network.

Networks page with the Create Network button

Step 2. Name the Network​

Type a memorable name (e.g. prod-net, staging-net, dmz-net) and click Create Network.

Network name form

The new Network has no subnet yet — add a subnet before VMs can attach to it.

Add a Subnet to the Network​

Step 1. Open the Subnet form​

In the Network list, click + next to the Network → Add Subnet.

Add subnet button on a Network

Step 2. Configure the subnet​

FieldMeaningExample
Subnet nameMemorable nameapp-tier
Network addressCIDR for the subnet192.168.100.0/24
GatewayInternal gateway IP192.168.100.1
Disable gatewayTick if the subnet has no gateway (rare)–
DHCPEnable to auto-assign IPs to VMsOn
Allocation PoolDHCP-managed IP range192.168.100.10 – 192.168.100.200
DNSDNS servers for VMs on this subnet8.8.8.8, 1.1.1.1
Host RoutesStatic routes added to VMs–

Subnet configuration form

Avoid default-gateway conflicts

A VM attached to multiple subnets that all have a gateway will end up with multiple default routes → unpredictable routing and possibly lost connectivity. Safe rule:

  • One default gateway per VM — only the "Internet-bound" subnet should have a gateway.
  • Other internal subnets tick Disable gateway, or simply don't attach them to that VM.

Step 3. Confirm​

Once created, the subnet appears in the Subnet block of the Network. From now on, VMs can attach to it during creation or via Network Interface.

Subnet created inside the Network

Common topologies​

A single subnet​

For small projects — all VMs share 10.0.0.0/24, leave through the Router with S-NAT enabled.

Application + database split​

  • app-subnet (10.0.1.0/24) — app VMs, gateway on, Floating IPs attached.
  • db-subnet (10.0.2.0/24) — database VMs, no Floating IP, no gateway → only the app VMs in the same Network can reach them.

Dedicated management network​

Add mgmt-subnet (10.0.99.0/24) for SSH/RDP and monitoring, separate from the data plane to shrink the attack surface.

See also​