Virtual Network

The Virtual Network (VNET) is the foundational building block of the Wanscale Platform. It serves as the central intelligence hub for your environment, performing several critical functions:

Routing Management: Maintains the Routing Information Base (RIB).
Cloud Integration: Manages BGP sessions to external services such as Azure or AWS.
Static Routing: Handles static routes for services like LAN locations behind a Service Edge.
SD-WAN Control: Manages WAN Interface Groups used for Path Selection on Service Edges.
Policy Enforcement: Centralizes management for:
- 1:1 DNAT
- Firewall Rules
- Path Selection
- Source NAT (SNAT)

Tip

You can have multiple VNETs per tenant

VNET Requirements

Before creating a VNET, ensure you have an appropriate IPv4 Address Space available. This space is used by the platform to facilitate internal connectivity between services.

Warning

This Address Space cannot overlap with IP addresses or prefixes you use elsewhere in your network. It must be unique in the VNET RIB

Creating a VNET

Follow these steps to deploy a new Virtual Network:

Navigate to the Home page of the Wanscale Platform.
Click the Add Service button.
Select Virtual Network from the service list.
Click Go to service form.
Complete the following fields in the service form:
- Label: Enter a descriptive name for the VNET.
- Tags (Optional): Add metadata for easier filtering.
- Zone: Select the Geographic Zone where the VNET resources will be provisioned.
- Address Space: Enter a unique IPv4 prefix for your RIB.
Click Submit

Tip

Sizing Recommendation: We suggest using an RFC1918 or CGNAT prefix no smaller than a /22.

Each service attached to the VNET can consume up to four /30 prefixes.
A /22 supports approximately 64 services, while a /16 supports 4,096.
Note: This prefix cannot be changed after the VNET is created.

Note

Applying Changes: Like all networking services in the portal, your new VNET will not be active until you deploy the changes. See Workflows and Applying Changes.