​
Overview

Networking is where you define private address space, control what can reach your machines, and connect locations together.
Navigation: Networking.

​
Screens in this area

​
VPC

A VPC is an isolated private address space in one availability zone. Inside it are networks, each with a gateway and a usable IP range, and your machines attach to those networks. Every zone your account uses gets its own VPC — they are not shared across zones. See Regions and zones. Each VPC has a detail page with tabs for its networks and related resources.
Two VPC detail tabs are not yet available: routing (route table configuration) and security. Both read “coming soon”. The subnets tab is also incomplete — it does not yet list the VPC’s networks reliably. Use the VPC’s own networks view for an accurate picture.
Networks are managed through their VPC. A standalone Networks list existed previously and has been withdrawn — VPC is now the single entry point. Individual network detail pages are still reachable by following links from other resources, but the Configure Network and Monitor Network actions on those pages are not yet available.

​
Public IPs

By default a machine has a private address and is unreachable from the internet. Publishing it is a deliberate two-part act: acquire a public IP in the machine’s zone, then map it to the machine with Static NAT.
Static NAT is the only inbound service available in the current phase. Load balancing and port forwarding are both switched off, and their controls are hidden from this screen — the row menu, the details tab, and the create-rule dialog. In practice this means one public IP serves one machine, and publishing several services behind one address isn’t possible yet.
Public IPs count against your network quota whether or not they’re mapped to anything, so release ones you aren’t using.

​
Firewall Policies

Firewall policies are the rule sets that decide what traffic is allowed. Mapping a public IP to a machine makes it addressable; the firewall policy decides what’s actually allowed through.
This screen is labelled Firewall Policies in the console, but the underlying resource is a network ACL — you’ll see that name in the API and in URLs. Same thing.
Open only the ports you need. Publishing a machine and leaving the range open is the most common way to expose something unintentionally.

​
Site-to-Site VPN and Customer Gateways

Together these connect a Simnet VPC to a network you run somewhere else. A customer gateway describes the remote end — its address and connection parameters — and a site-to-site VPN connection is the tunnel to it. Define the customer gateway first, then create the connection that references it.

​
Fabric

Fabric shows your footprint on a world map and manages private connections between your VPCs, riding the VPN gateway each zone was given when it was deployed. Connected VPCs reach each other over private addresses without traversing the public internet.
Fabric connections are currently limited to VPCs in different availability zones of the same region. Connecting VPCs in two different regions is not yet supported, even though the map shows your whole footprint.
Several Fabric features are built but withheld: Clouds (grouping VPCs into cloud contexts), the map lens (layer toggles and legend), proximity banding, and VPC search. They aren’t in the interface yet. Fabric currently ships as the global map plus VPC-to-VPC connections.
Fabric replaces the earlier Multi-Region page, which no longer exists — old links land on Fabric.
Fabric also depends on a platform capability being enabled for your deployment. If it’s switched off, the screen isn’t in your sidebar at all.

​
Putting it together

Regions and zones

Why there’s one VPC per zone.

Compute

The machines that attach to these networks.

Quickstart

Create a VPC, network, and public IP in order.