Static Routes

Static routes are used to route traffic to various interfaces which were not learned by the routing protocols. For example, route specific subnet via the WAN, LAN or Tunnel. Follow the steps detailed below to add static routes to flexiEdge.

In order to define a static route for a given flexiEdge device, click on the device name and go to the “Static Routes” tab.

Static Routes

Click on “Add Route” and add the static route details for the subnet and mask, gateway and interface. If the gateway is within a subnet of one of the router interfaces, the interface specification is optional.

At the moment, the tunnel interfaces are not shown in the add static route form. So routes via tunnels must be defined without an interface. To define a static route via the tunnel, create the tunnel, make sure it is connected and get the tunnel loopback address from the Inventory -> Tunnels menu. Define the static route using the loopback address.

After creating a static route, the static routes are shown in the table with a status of the provisioning

Static Routes Table

The status can be one of the following:

  • waiting - when the job scheduled to be sent to flexiEdge

  • complete - when the static route being successfully provisioned into flexiEdge

  • add-failed - when the static route failed to be provisioned. A button will show up to re-send the route

  • remove-failed - when deleting the static route failed

  • job-deleted - when the scheduled job was deleted from the Troubleshooting -> Jobs menu