You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn how to configure the Linux (strongSwan) VPN client solution for VPN Gateway P2S configurations that use certificate authentication. This article applies to Linux (strongSwan).
4
+
description: Learn how to configure a Linux VPN client solution for VPN Gateway P2S configurations that use certificate authentication.
# Configure point-to-site VPN clients - certificate authentication - Linux
13
13
14
-
When you connect to an Azure virtual network (VNet) using point-to-site (P2S) and certificate authentication from a Linux computer, you can use strongSwan. All of the necessary configuration settings for the VPN clients are contained in a VPN client configuration zip file. The settings in the zip file help you easily configure the VPN clients Linux.
14
+
When you connect to an Azure virtual network (VNet) using point-to-site (P2S) and certificate authentication from a Linux computer, you can use strongSwan (IKEv2 tunnels) or an OpenVPN client. All of the necessary configuration settings for the VPN clients are contained in a VPN client configuration zip file. The settings in the zip file help you easily configure the VPN clients Linux.
15
15
16
16
The VPN client configuration files that you generate are specific to the P2S VPN gateway configuration for the virtual network. If there are any changes to the P2S VPN configuration after you generate the files, such as changes to the VPN protocol type or authentication type, you need to generate new VPN client configuration files and apply the new configuration to all of the VPN clients that you want to connect. For more information about P2S connections, see [About point-to-site VPN](point-to-site-about.md).
17
17
@@ -21,63 +21,37 @@ Before beginning, verify that you are on the correct article. The following tabl
A client certificate is required for authentication when using the Azure certificate authentication type. A client certificate must be installed on each client computer. The exported client certificate must be exported with the private key, and must contain all certificates in the certification path. Make sure that the client computer has the appropriate client certificate installed before proceeding to the next section.
36
-
37
-
For information about client certificates, see [Generate certificates - Linux](vpn-gateway-certificates-point-to-site-linux.md).
You can generate client configuration files using PowerShell, or by using the Azure portal. Either method returns the same zip file.
42
27
43
-
### <aname="portal"></a>Generate profile config files using the Azure portal
44
-
45
-
1. In the Azure portal, navigate to the virtual network gateway for the virtual network that you want to connect to.
46
-
1. On the virtual network gateway page, select **Point-to-site configuration** to open the Point-to-site configuration page.
47
-
1. At the top of the Point-to-site configuration page, select **Download VPN client**. This doesn't download VPN client software, it generates the configuration package used to configure VPN clients. It takes a few minutes for the client configuration package to generate. During this time, you may not see any indications until the packet has generated.
28
+
### View the folder and files
48
29
49
-
:::image type="content" source="./media/point-to-site-vpn-client-cert-linux/download-configuration.png" alt-text="Download the VPN client configuration." lightbox="./media/point-to-site-vpn-client-cert-linux/download-configuration.png":::
50
-
1. Once the configuration package has been generated, your browser indicates that a client configuration zip file is available. It's named the same name as your gateway.
51
-
52
-
### <aname="powershell"></a>Generate profile config files using PowerShell
53
-
54
-
1. When generating VPN client configuration files, the value for '-AuthenticationMethod' is 'EapTls'. Generate the VPN client configuration files using the following command:
***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.
33
+
***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 isn’t present.
58
34
59
-
$profile.VPNProfileSASUrl
60
-
```
35
+
## Select the configuration instructions
61
36
62
-
1. Copy the URL to your browser to download the zip file.
37
+
The sections below contain instructions to help you configure your VPN client. Select the tunnel type that your P2S configuration uses, then select the method that you want to use to configure.
63
38
64
-
## 4. View the folder and files
39
+
*[IKEv2 tunnel type steps](#ike) for strongSwan
40
+
*[OpenVPN tunnel type steps](#openvpn) for OpenVPN client
65
41
66
-
Unzip the file to view the following folders:
42
+
## <aname="ike"></a>IKEv2 - strongSwan steps
67
43
68
-
***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.
69
-
***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 isn’t present.
The sections below contain instructions to help you configure your VPN client. Select the tunnel type that your P2S configuration uses, then select the method that you want to use to configure.
48
+
### Install certificates
74
49
75
-
*[IKEv2 tunnel type steps](#ike)
76
-
*[OpenVPN tunnel type steps](#openvpn)
50
+
A client certificate is required for authentication when using the Azure certificate authentication type. A client certificate must be installed on each client computer. The exported client certificate must be exported with the private key, and must contain all certificates in the certification path. Make sure that the client computer has the appropriate client certificate installed before proceeding to the next section.
77
51
78
-
## <aname="ike"></a>IKEv2 tunnel type steps
52
+
For information about client certificates, see [Generate certificates - Linux](vpn-gateway-certificates-point-to-site-linux.md).
79
53
80
-
This section helps you configure Linux clients for certificate authentication that uses the IKEv2 tunnel type. To connect to Azure, you manually configure an IKEv2 VPN client.
54
+
### View VPN client profile files
81
55
82
56
Go to the downloaded VPN client profile configuration files. You can find all of the information that you need for configuration in the **Generic** folder. Azure doesn’t provide a *mobileconfig* file for this configuration.
83
57
@@ -91,7 +65,12 @@ The Generic folder contains the following files:
91
65
***VpnSettings.xml**, which contains important settings like server address and tunnel type.
92
66
***VpnServerRoot.cer**, which contains the root certificate required to validate the Azure VPN gateway during P2S connection setup.
93
67
94
-
### <aname="gui"></a>GUI instructions
68
+
After viewing the files, continue with the steps that you want to use:
69
+
70
+
*[GUI steps](#gui)
71
+
*[CLI steps](#cli)
72
+
73
+
#### <aname="gui"></a>strongSwan GUI instructions
95
74
96
75
This section walks you through the configuration using the strongSwan GUI. The following instructions were created on Ubuntu 18.0.4. Ubuntu 16.0.10 doesn’t support strongSwan GUI. If you want to use Ubuntu 16.0.10, you’ll have to use the [command line](#linuxinstallcli). The following examples may not match screens that you see, depending on your version of Linux and strongSwan.
97
76
@@ -126,7 +105,7 @@ This section walks you through the configuration using the strongSwan GUI. The f
0 commit comments