- Home /
- Resources /
- Learning center /
- Internal Network O...
Internal Network Only with no Internet Access
Networking Architecture (Scenario 2) - Exploring network configurations where every device is connected to each other but not to the Internet

On this page
In this scenario:
- Devices are not connected to the Internet
- There are no Internet connections
- Devices communicate with each other via standard Equinix Metal networking
- Devices use private IPs allocated by Equinix Metal
- Devices may be all in one metro or in multiple metros
Each and every device receives only a private IPv4 address. Each device is on its own private subnet, to which just the device and its upstream router are connected.
Without a public address, the device cannot communicate with the Internet, but it and can communicate with other devices in the same project using its private address or the public address.
The private addresses are provided and managed by Equinix Metal.
Multiple Metros
If you wish to deploy devices in multiple metros while enabling communications between them, you cannot communicate over the Internet, with or without a VPN, as the devices have no Internet connectivity.
Your sole option is to enable Backend Transfer.
You may also like
Dig deeper into similar topics in our archives
Crosscloud VPN with WireGuard
Learn to establish secure VPN connections across cloud environments using WireGuard, including detailed setups for site-to-site tunnels and VPN gateways with NAT on Equinix Metal, enhancing...

Kubernetes Cluster API
Learn how to provision a Kubernetes cluster with Cluster API

Kubernetes with kubeadm
Learn how to deploy Kubernetes with kubeadm using userdata

OpenStack DevStack
Use DevStack to install and test OpenStack on an Equinix Metal server.