Network
Public network
A network with internet access, to which all servers are physically connected. On some TCP and UDP ports, network traffic between the private network and the internet is limited.
When working with a public network and internet access, make sure to comply with the terms of use.
Private network
A local network to which all servers are connected. Logically joins servers into isolated user networks.
Private subnet
A network physically bounded by the network equipment of a single pool, isolated both from the internet and from other users' networks.
Within a single pool, L2 connectivity (VLAN) and L3 connectivity (VRF) are possible between leased servers. Between servers physically hosted in different pools, only L3 connectivity is available.
To configure networking between servers from different pools, select the same VRF for the appropriate subnets under Routing settings.
For subnet addressing purposes, you can use any CIDR in the ranges reserved for private networks: 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16. The subnet must include at least eight addresses (the maximum CIDR prefix length is /29).
Virtual network segment (VRF)
To provide L3 routing, private subnets with configured routing are aggregated into virtual network segments (VRFs).
Servers from the same or different pools connected to different private subnets aggregated into a VRF segment will be able to maintain L3 networking between them.
Private connection to cloud networks
To set up network connectivity between BareMetal servers, Yandex Virtual Private Cloud private subnets, and private subnets in the on-premise infrastructure, use Yandex Cloud Interconnect.