Static Routing

Static Routing allows you to manually define paths for network traffic within the Wanscale Platform. While the platform handles much of the routing automatically, static routes are essential for directing traffic toward networks or devices that aren't dynamically learned.

Prerequisites

Before configuring a Static Route, ensure you have:

• A Virtual Network (VNET) already deployed.
• A Service Edge (SE) or DC Connect that will serve as the gateway for the route.
• The Destination Prefix (in CIDR notation) and the Next Hop IP address.

Configuring a Static Route

Follow these steps to add a static route to your VNET:

1. Navigate to the Services page and select your VNET.
2. In the left sidebar, expand Policies and select Static Routing.
3. Click the Add button.
4. Complete the following fields in the configuration screen:
   • Label: Enter a descriptive name for the route (e.g., "Internal Database Subnet").
   • Destination: Enter the destination network address in CIDR notation (e.g., 192.168.50.0/24).
   • Next Hop: Enter the IP address of the gateway or interface that should receive traffic for this prefix.
   • Source (Optional): Provide a prefix if you want to use source based routing.
5. Click Save.

Route Priority and Conflicts

The platform's Routing Information Base (RIB) evaluates routes based on specificity. A more specific route (e.g., a /32 host route) will always take precedence over a less specific one (e.g., a /24 subnet route).