OpenVPN Gateway

How do I generate an .ovpn file for my SAML VPN users?

Once you enable SAML auth for an OpenVPN gateway, you need to create a dummy user on the controller to generate an .ovpn file – you can share this file with all of your users. As the second authentication is through SAML, this should provide good security. This is per VPC+ELB/GW setup. If you have more than one such deployed VPC+ELB/GW setups, you would need a .ovpn file for each of those setups.

Can I connect vi multiple VPN sessions from the same PC using Aviatrix VPN Client?

Currently we do not support multiple VPN sessions from the same pc via the Aviatrix VPN Client

Which VPN Clients are supported with SAML authentication?

At this time, we support SAML authentication for our VPN clients only for our Aviatrix VPN Client

Can I set a profile for my VPN user via SAML?

You can add a custom attribute “Profile” in your IdP and the value will be passed to the Aviatrix OpenVPN gateway during authentication. Aviatrix controller will then attach the Profile provided by the IdP to the VPN user. Currently we only allow one profile value to be passed via SAML auth. This will override any local settings on the controller for this user.

Can I assign multiple profiles to the same users?

You can assign multiple profiles to a VPN user - but, please make sure that they all have the same base policies (allow all or deny all)

How to delete a Network Load Balancer which is created by Aviatrix?

An ELB will be automatically deleted by the Aviatrix Controller if all the gateways behind it are deleted and if there are no more users attached to it. The last resort to delete an ELB is delete it from Troubleshoot > ELB.

Should I be worried about Tunnelblick VPN Client’s warning message about “comp-lzo”?

Tunneblick VPN Client might show a warning about “comp-lzo” being deprecated when connecting to Aviatrix OpenVPN Gateway. You can safely ignore this message. We have kept this option in for backward compatibility

Any known issue with DD-WRT routers?

Aviatrix VPN Client needs to be able to resolve localhost.aviatrix.com to 127.0.0.1. DD-WRT router is known to have an issue resolving this, so your VPN connection might fail. Please take a look at this link for a workaround.

What should I do if Aviatrix VPN Client displays “Permission Denied” error?

If you encounter “Permission Denied” error while starting Aviatrix VPN Client on Microsoft Windows, you can fix this by running it with administrator role. Here are the steps for Windows 10:

  • From Start Menu, find Aviatrix VPN Client. Right-click and select Open File Location.
  • Right-click the program and go to Properties.
  • On the Properties window, click the Compatibility tab.
  • Under the Compatibility mode section, check the “Run as administrator” checkbox.
  • Click the OK button to save the settings and start the program again.

Looking for an easy LDAP solution for Aviatrix OpenVPN Solution?

Check out AWS’s LDAP

How can I scale my VPN user setup?

Deploy your Aviatrix OpenVPN Gateway’s behind a Load Balancer so you can scale up by adding more VPN gateways behind the ELB, when needed, and don’t have to worry about losing IP address and having to reissue certificates to all of your VPN users.

How can the OpenVPN made Highly Available?

We have HA built into our OpenVPN system. By default the OpenVPN gateways are deployed behind a Load Balancer in AWS. When you deploy additional OpenVPN gateways in the same VPC, they are deployed behind the same ELB, so the system becomes HA and resilient to any failures.

Here are instructions to use LB with UDP OpenVPN sessions.

How does a vpn client access resources from different VPCs when connecting to OpenVPN gateway?

Be default, split VPN clients can only reach the VPC that the OpenVPN gateway is deployed. If you want them to reach other VPC’s, please add them to “VPN CIDR” - instructions

If OpenVPN is enabled on a Spoke Gateway in Transit Network, can my VPN users access other Spoke’s resources?

In a Transit solution, note that traffic between spokes is not allowed and hence your clients will not be able to reach other spoke VPC’s - checkout “Connected Mode”. Also traffic from Transit VPC is also not advertised by default.

We recommend that you deploy OpenVPN on a separate Gateway to take advantage of the Load Balancer for scalability.

Why do my VPN clients take longer to connect, sometimes?

Sometimes the clients might take some time to connect due to ELB’s load - check the logs on the client.

Why are my DNS settings changes not taking effect?

In the case of a full tunnel deployment, if an OpenVPN Gateway is edited to toggle the “Use VPC/VNet DNS Server” setting, please follow it by clicking on OpenVPN/EditConfig/ReloadDHCPConfiguration to let the changes take effect. Note that this will restart the OpenVPN processes on the gateway, affecting all the connected clients. The DNS settings are shared with an OpenVPN user only in a Full tunnel setup and not for split tunnel setup.

How can I send the VPN config files to my users?

By default, when you add the email address to a user, they will receive the VPN config file (.ovpn) via email. If you do not want to share these files via email, please do not enter the email address for the vpn users. You can then download these files, one at a time from the Controller, UI per user. You can use our REST API - and then share it via your preferred mechanism with your VPN user. The REST API allows you to scale up if you deploy it via automation.

How can I customize the email that is sent out when a new VPN user is added?

You can customize the message of the email and the filename of the .ovpn file by following the instructions here. We will enhance this feature in future to allow you to customize the subject as well, stay tuned.

My Mac is not picking up the DNS server setting when connected?

The OpenVPN gateway will push the DNS setting to the vpn clients (by default for full tunnel and when configured for split-tunnel). If the Mac has the DNS configured manually, then it cannot be overwritten by the VPN Client. We have a couple of workarounds for this issue

  • Turn on the “Allow override of manually set DNS” option in the VPN Client / Advanced / Advanced
  • Change the DNS setting on your Mac so that it will be picked up from the DHCP server