Launch a NetFoundry Gateway in Azure Stack


This install guide will walk you through the steps required to launch a NetFoundry Gateway instance in your Azure VNET.

Getting Started

1. Sign in to your account on the Azure portal.

2. Go to → Resource groups.

3. If you haven't already created a resource group, do so now or choose an existing one. 

4. Once inside the resource group, Click the "+ Add" button on the toolbar.

5. Search for "NetFoundry Azure Application Connection Gateway".

6. Click on the result, the description should be shown.

7. Click the "Create" button to launch the wizard:

  • Enter the "Name" (ex. NetFoundryGW).
  • VMdisk type, both are supported. PremiumSSD is default
  • Enter the Username as "nfadmin".
  • Enter your SSH Public Key, if you don't already have a global key or, provide a password.
  • Select your subscription.
  • Create a new resource group or select an existing one.
  • Choose a location to launch the VM in.
  • Click on "OK" to continue,


The username must be "nfadmin" to gain access to this gateway.

8. Select a size and click on "Select" (ex. A1 Standard).

9. Finalize the details, and click "Ok" to continue.

10. Click on "Create" to launch the gateway

11. Once the resource is created, go to the resource group & click on the virtual machine name to view the details. Locate the machine's public IP address

12. Using an SSH client, log in to the machine using its public IP address as the user "nfadmin", using the SSH key or password specified earlier.

Example: OpenSSH
ssh -i <path/to/private/key> nfadmin@<public_ip_address>

If you already have a specific network to launch within, you can select it here. Otherwise Azure will launch into a new network & create a network rule to allow SSH access inbound.   


13. Once you are logged in to the gateway, run these commands to register it to your NetFoundry Network. Look for errors in the registration process output, or "Success" if registration completes successfully.

> sudo su
> /opt/dispersive/dvn/nfnreg -e production [registration key]
> systemctl status dvn.service


You must become root in order for the nfreg command to become available for use!

14. Validate that the VM is now active on the NetFoundry Network with the following command:

> systemctl status dvn.service

The output should report "ACTIVE".

Most common causes for registration to fail are: Not having an IP assigned (correctly), Not having a working default gateway for Internet access, Not having a valid DNS resolver.

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



Article is closed for comments.