Infrastructure Networking

Internet is the default path out. Private networks are extra.

A first server attaches to Internet on the create form. That is how it gets a public IPv4. You do not create that network on this page. See Creating and Managing Virtual Machines.

Cloud → Networking is private networks, ports, routers, floating IPs, load balancers, and security groups. The firewall how-to is Using Security Groups.

Networks

The Networks tab lists networks you created. A new project can show No Rows To Show. + Create Network adds a private network when you need isolation (app vs db, or a network that is not the Internet). Subnets and routers live on those networks after you create them.

1. Click + Create Network.
2. Location is SiouxFalls.
3. Name it. Description is optional.
4. Leave Subnet on to get a CIDR. The form prefills 10.0.1.0/24.
5. Turn on Enable DHCP if instances should get addresses automatically.
6. Turn on Gateway only if this subnet needs one.
7. Allocation Pools, DNS Name Servers, and Host Routes are optional.
8. Then create the network.

Skip Internet on the VM and you will not have a public SSH path unless you add another route later.

On the server

The server page has Networking. Overview already shows the public IPv4 and Network Internet. Extra interfaces show up there after you attach them.

The other tabs

• Ports are the NICs. Your first VM already has one.
• Subnets and Routers are for private networks you create.
• Floating IPs are extra public addresses you allocate and associate. Not required if the instance is already on Internet.
• Load Balancers and VPNs are for later, not a first server.
• Security Groups — follow Using Security Groups.