Configure Azure Route Tables to Use a NetFoundry Gateway for Egress to Azure Virtual WAN

Azure Route Tables allow you to specify network routes so that the NetFoundry Gateway will pass traffic from your Branch Virtual Network to the Azure Virtual WAN. In order for network interfaces to do this, routes must be specified and IP forwarding must be enabled in Azure. IP forwarding has already been enabled on your pre-built NetFoundry image. When multiple routes are present for a given destination, the more specific route is utilized. 


Log into the Azure Portal:


Create the Route Table


Create the route table in the Resource Group and Location of the Remote Site location. 

1. Select + Create a resource in the upper left corner.

2. Select Networking and then select Route table.

3. Enter the following information and disable BGP.

- Create a name without spaces.

- Select Resource Group where your remote site resources are grouped.

- Select a Location where your remote site is located within Azure.



Create a Route


1. From within the selected Resource Group listing, select the route table created in the previous step.

2. Under Settings, select Routes and select + Add.


3. Enter the following information and disable BGP.

- Create a name without spaces.

- CIDR notation for the network in the Azure Cloud connected to the HUB.

- Select Virtual Appliance

- IP Address of the NetFoundry Gateway (Private).




Associate Subnet to Route Table


 1. After you have created the route table, Select Subnets from the Route Table dashboard in the middle pane and select + Associate.




2. Select the Subnet name associated with your Branch site Virtual Network and the default subnet. Hit Ok.




Enable IP Forwarding on Gateway

1. From within the selected Resource Group listing, search for the Network Interface for the NetFoundry Gateway Virtual Machine and select it.




2. Select IP Configurations from the middle panel. Then select Enabled for IP Networking settings and hit save.




3. You should now be able to access resources in the Azure Cloud from a host behind a NetFoundry Gateway. 


Was this article helpful?
2 out of 2 found this helpful



Article is closed for comments.