Updated 1/22/21 to include our review of FastestVPN, a no-nonsense, easy-to-use VPN that probably won’t appeal to power users, but is a good option for new VPN users—so much so.
- Client Openvpn For Mac Os X Catalina
- Openvpn Mac Os Download
- Client Openvpn For Mac Os X 32-bit
- Openvpn Client For Mac Os X
There are three client options for Mac OS X.:
- The OpenVPN command line client. Most users prefer a graphical client, so thisoption will not be covered.
- Tunnelblick, a free option available for download at the Tunnelblick Website. Simcity for mac free.
- The commercial Viscosity client. At the time of this writing, it costs $14USD for a single seat. If OpenVPN is used frequently, Viscosity is a muchnicer client and well worth the cost.
- How to use #AllNewPureVPN App for Mac. Connect to our Recommended Location or click the Globe icon to connect to the location of your choice. Select a VPN server location from the list of countries. Once connected, you can access, browse, stream, and download with privacy & security.
- Since a VPN encrypts internet traffic, all your online data remains hidden from online spies. On the other hand, if you watch movies on your laptop, you may also need a VPN client for your Mac.
- There are three client options for Mac OS X.: The OpenVPN command line client. Most users prefer a graphical client, so thisoption will not be covered. Tunnelblick, a free option available for download at the Tunnelblick Website. The commercial Viscosity client. At the time of this writing, it costs $14USD for a single seat.
Both Tunnelblick and Viscosity are easily installed, with no configurationoptions during installation.
Configuring Viscosity¶
When using the Viscosity client, it can be configured manually or the OpenVPNClient Export package may be used to import the configuration. Viscosityprovides a GUI configuration tool that can be used to generate the underlyingOpenVPN client configuration. The CA and certificates can be imported manually,and all of the parameters can be set by hand. This section cover importing aViscosity bundle from the export package.
- Download a copy of the Viscosity bundle for the client from the OpenVPNClient Export package
- Locate the saved file, which will end in
.visc.zip
indicating that it is acompressed archive - Copy this exported bundle to a folder on the Mac
- Double click this file and it will expand to
Viscosity.visc
- Double click
Viscosity.visc
and Viscosity will open and import theconnection as shown in Figure Viscosity Import
- Delete the
Viscosity.visc
directory and the.zip
archive - Viscosity will be running after import, and may be found in the menu bar
- Click the lock icon added to the menu bar at the top of the screen
- Click Preferences to check that the configuration was imported as shown inFigure Viscosity Preferences
Viscosity Preferences¶
- Check the Connections area to see if the connection imported successfullyas shown in Figure Viscosity View Connections.
- Close the Preferences screen
- Click the lock in the menu bar
- Click the name of the VPN connection to connect as shown in FigureViscosity Connect. After a few seconds, the lock in the menu barwill turn green to show it connected successfully.
Viscosity Connect¶
- Click on it and then click Details as shown in FigureViscosity Menu to see connection information
On the first screen (Figure Viscosity Details), the connectionstatus, connected time, the IP assigned to the client, and the IP of the serverare all displayed. A bandwidth graph is displayed at the bottom of the screen,showing the throughput in and out of the OpenVPN interface.
Viscosity Details¶
Clicking the up/down arrow button in the middle of the details screen displaysadditional network traffic statistics. This shows the traffic sent within thetunnel (TUN/TAP In and Out), as well as the total TCP or UDP traffic sentincluding the overhead of the tunnel and encryption. For connections usingprimarily small packets the overhead is considerable with all VPN solutions. Thestats shown in Figure Viscosity Details: Traffic Statistics are from only afew pings traversing the connection. The traffic sent in bringing up theconnection is also counted here, so the initial overhead is higher than what itwill be after being connected for some time. Also, the typical VPN traffic willhave larger packet sizes than 64 byte pings, making the total overhead anddifference between these two numbers considerably less.
Clicking on the third icon in the middle of the Details screen shows theOpenVPN log file (Figure Viscosity Details: Logs). If there is any troubleconnecting, review the logs here to help determine the problem. See alsoTroubleshooting OpenVPN.
Viscosity Details: Logs¶
-->VPN client configuration files are contained in a zip file. Configuration files provide the settings required for a native Windows, Mac IKEv2 VPN, or Linux clients to connect to a virtual network over Point-to-Site connections that use native Azure certificate authentication.
Client configuration files are specific to the VPN configuration for the virtual network. If there are any changes to the Point-to-Site VPN configuration after you generate the VPN client configuration files, such as the VPN protocol type or authentication type, be sure to generate new VPN client configuration files for your user devices.
- For more information about Point-to-Site connections, see About Point-to-Site VPN.
- For OpenVPN instructions, see Configure OpenVPN for P2S and Configure OpenVPN clients.
Important
Starting July 1, 2018, support is being removed for TLS 1.0 and 1.1 from Azure VPN Gateway. VPN Gateway will support only TLS 1.2. Only point-to-site connections are impacted; site-to-site connections will not be affected. If you’re using TLS for point-to-site VPNs on Windows 10 clients, you don’t need to take any action. If you are using TLS for point-to-site connections on Windows 7 and Windows 8 clients, see the VPN Gateway FAQ for update instructions.
Generate VPN client configuration files
Before you begin, make sure that all connecting users have a valid certificate installed on the user's device. For more information about installing a client certificate, see Install a client certificate.
You can generate client configuration files using PowerShell, or by using the Azure portal. Either method returns the same zip file. Unzip the file to view the following folders:
- WindowsAmd64 and WindowsX86, which contain the Windows 32-bit and 64-bit installer packages, respectively. The WindowsAmd64 installer package is for all supported 64-bit Windows clients, not just Amd.
- Generic, which contains general information used to create your own VPN client configuration. The Generic folder is provided if IKEv2 or SSTP+IKEv2 was configured on the gateway. If only SSTP is configured, then the Generic folder is not present.
Generate files using the Azure portal
- In the Azure portal, navigate to the virtual network gateway for the virtual network that you want to connect to.
- On the virtual network gateway page, select Point-to-site configuration.
- At the top of the Point-to-site configuration page, select Download VPN client. It takes a few minutes for the client configuration package to generate.
- Your browser indicates that a client configuration zip file is available. It is named the same name as your gateway. Unzip the file to view the folders.
Generate files using PowerShell
- When generating VPN client configuration files, the value for '-AuthenticationMethod' is 'EapTls'. Generate the VPN client configuration files using the following command:
- Copy the URL to your browser to download the zip file, then unzip the file to view the folders.
Windows
You can use the same VPN client configuration package on each Windows client computer, as long as the version matches the architecture for the client. For the list of client operating systems that are supported, see the Point-to-Site section of the VPN Gateway FAQ.
Note
You must have Administrator rights on the Windows client computer from which you want to connect.
Use the following steps to configure the native Windows VPN client for certificate authentication:
- Select the VPN client configuration files that correspond to the architecture of the Windows computer. For a 64-bit processor architecture, choose the 'VpnClientSetupAmd64' installer package. For a 32-bit processor architecture, choose the 'VpnClientSetupX86' installer package.
- Double-click the package to install it. If you see a SmartScreen popup, click More info, then Run anyway.
- On the client computer, navigate to Network Settings and click VPN. The VPN connection shows the name of the virtual network that it connects to.
- Before you attempt to connect, verify that you have installed a client certificate on the client computer. A client certificate is required for authentication when using the native Azure certificate authentication type.
Mac (OS X)
You have to manually configure the native IKEv2 VPN client on every Mac that will connect to Azure. Azure does not provide mobileconfig file for native Azure certificate authentication. The Generic contains all of the information that you need for configuration. If you don't see the Generic folder in your download, it's likely that IKEv2 was not selected as a tunnel type. Note that the VPN gateway Basic SKU does not support IKEv2. Once IKEv2 is selected, generate the zip file again to retrieve the Generic folder.
The Generic folder contains the following files:
The Generic folder contains the following files:
- VpnSettings.xml, which contains important settings like server address and tunnel type.
- VpnServerRoot.cer, which contains the root certificate required to validate the Azure VPN Gateway during P2S connection setup.
Use the following steps to configure the native VPN client on Mac for certificate authentication. You have to complete these steps on every Mac that will connect to Azure:
- Import the VpnServerRoot root certificate to your Mac. This can be done by copying the file over to your Mac and double-clicking on it. Select Add to import.NoteDouble-clicking on the certificate may not display the Add dialog, but the certificate is installed in the correct store. You can check for the certificate in the login keychain under the certificates category.
- Verify that you have installed a client certificate that was issued by the root certificate that you uploaded to Azure when you configured you P2S settings. This is different from the VPNServerRoot that you installed in the previous step. The client certificate is used for authentication and is required. For more information about generating certificates, see Generate Certificates. For information about how to install a client certificate, see Install a client certificate.
- Open the Network dialog under Network Preferences and select '+' to create a new VPN client connection profile for a P2S connection to the Azure virtual network.The Interface value is 'VPN' and VPN Type value is 'IKEv2'. Specify a name for the profile in the Service Name field, then select Create to create the VPN client connection profile.
- In the Generic folder, from the VpnSettings.xml file, copy the VpnServer tag value. Paste this value in the Server Address and Remote ID fields of the profile.
- Select Authentication Settings and select Certificate. For Catalina, select None, and then certificate.For Catalina, select None and then Certificate. Select the correct certificate:
- Click Select… to choose the client certificate that you want to use for authentication. This is the certificate that you installed in Step 2.
- Choose An Identity displays a list of certificates for you to choose from. Select the proper certificate, then select Continue.
- In the Local ID field, specify the name of the certificate (from Step 6). In this example, it is
ikev2Client.com
. Then, select Apply to save the changes. - On the Network dialog, select Apply to save all changes. Then, select Connect to start the P2S connection to the Azure virtual network.
Linux (strongSwan GUI)
Install strongSwan
The following configuration was used for the steps below:
- Computer: Ubuntu Server 18.04
- Dependencies: strongSwan
Use the following commands to install the required strongSwan configuration:
Use the following command to install the Azure command-line interface:
Generate certificates
If you have not already generated certificates, use the following steps:
Generate the CA certificate.
Print the CA certificate in base64 format. This is the format that is supported by Azure. You upload this certificate to Azure as part of the P2S configuration steps.
Generate the user certificate.
Generate a p12 bundle containing the user certificate. This bundle will be used in the next steps when working with the client configuration files.
Install and configure
The following instructions were created on Ubuntu 18.0.4. Ubuntu 16.0.10 does not support strongSwan GUI. If you want to use Ubuntu 16.0.10, you will have to use the command line. The examples below may not match screens that you see, depending on your version of Linux and strongSwan.
Client Openvpn For Mac Os X Catalina
- Open the Terminal to install strongSwan and its Network Manager by running the command in the example.
- Select Settings, then select Network. Select the + button to create a new connection.
- Select IPsec/IKEv2 (strongSwan) from the menu, and double-click.
- On the Add VPN page, add a name for your VPN connection.
- Open the VpnSettings.xml file from the Generic folder contained in the downloaded client configuration files. Find the tag called VpnServer and copy the name, beginning with 'azuregateway' and ending with '.cloudapp.net'.
- Paste the name in the Address field of your new VPN connection in the Gateway section. Next, select the folder icon at the end of the Certificate field, browse to the Generic folder, and select the VpnServerRoot file.
- In the Client section of the connection, for Authentication, select Certificate/private key. For Certificate and Private key, choose the certificate and the private key that were created earlier. In Options, select Request an inner IP address. Then, select Add.
- Turn the connection On.
Linux (strongSwan CLI)
Install strongSwan
The following configuration was used for the steps below:
Openvpn Mac Os Download
- Computer: Ubuntu Server 18.04
- Dependencies: strongSwan
Use the following commands to install the required strongSwan configuration:
Use the following command to install the Azure command-line interface:
Client Openvpn For Mac Os X 32-bit
Generate certificates
If you have not already generated certificates, use the following steps:
Generate the CA certificate.
Openvpn Client For Mac Os X
Print the CA certificate in base64 format. This is the format that is supported by Azure. You upload this certificate to Azure as part of the P2S configuration steps.
Generate the user certificate.
Generate a p12 bundle containing the user certificate. This bundle will be used in the next steps when working with the client configuration files.
Install and configure
- Download the VPNClient package from Azure portal.
- Extract the file.
- From the Generic folder, copy or move the VpnServerRoot.cer to /etc/ipsec.d/cacerts.
- Copy or move cp client.p12 to /etc/ipsec.d/private/. This file is the client certificate for the VPN gateway.
- Open the VpnSettings.xml file and copy the
<VpnServer>
value. You will use this value in the next step. - Adjust the values in the example below, then add the example to the /etc/ipsec.conf configuration.
- Add the following values to /etc/ipsec.secrets.
- Run the following commands:
Next steps
Return to the original article that you were working from, then complete your P2S configuration.
- PowerShell configuration steps.
- Azure portal configuration steps.