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
Copy file name to clipboardExpand all lines: articles/vpn-gateway/moving-to-ikev2-or-openvpn-from-sstp.md
+40-40Lines changed: 40 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: 'Transition to OpenVPN or IKEv2 from SSTP | VPN Gateway'
2
+
title: 'Transition to OpenVPN or IKEv2 from SSTP | Azure VPN Gateway'
3
3
description: This article helps you understand the ways to overcome the 128 concurrent connection limit of SSTP.
4
4
services: vpn-gateway
5
5
author: anzaman
@@ -18,9 +18,9 @@ A Point-to-Site (P2S) VPN gateway connection lets you create a secure connection
18
18
19
19
Point-to-site VPN can use one of the following protocols:
20
20
21
-
***OpenVPN® Protocol**, an SSL/TLS based VPN protocol. An SSL VPN solution can penetrate firewalls, since most firewalls open TCP port 443 outbound, which SSL uses. OpenVPN can be used to connect from Android, iOS (versions 11.0 and above), Windows, Linux and Mac devices (OSX versions 10.13 and above).
21
+
***OpenVPN® Protocol**, an SSL/TLS based VPN protocol. An SSL VPN solution can penetrate firewalls, since most firewalls open TCP port 443 outbound, which SSL uses. OpenVPN can be used to connect from Android, iOS (versions 11.0 and above), Windows, Linux and Mac devices (OSX versions 10.13 and above).
22
22
23
-
***Secure Socket Tunneling Protocol (SSTP)**, a proprietary SSL-based VPN protocol. An SSL VPN solution can penetrate firewalls, since most firewalls open TCP port 443 outbound, which SSL uses. SSTP is only supported on Windows devices. Azure supports all versions of Windows that have SSTP (Windows 7 and later). **SSTP supports upto 128 concurrent connections only regardless of the gateway SKU**.
23
+
***Secure Socket Tunneling Protocol (SSTP)**, a proprietary SSL-based VPN protocol. An SSL VPN solution can penetrate firewalls, since most firewalls open TCP port 443 outbound, which SSL uses. SSTP is only supported on Windows devices. Azure supports all versions of Windows that have SSTP (Windows 7 and later). **SSTP supports up to 128 concurrent connections only regardless of the gateway SKU**.
24
24
25
25
* IKEv2 VPN, a standards-based IPsec VPN solution. IKEv2 VPN can be used to connect from Mac devices (OSX versions 10.11 and above).
26
26
@@ -59,8 +59,8 @@ Once the gateway has been configured,existing clients will not be able to connec
59
59
If you are using Windows 10, you can also use the [Azure VPN Client for Windows](https://docs.microsoft.com/azure/vpn-gateway/openvpn-azure-ad-client#to-download-the-azure-vpn-client)
60
60
61
61
62
-
# Frequently asked questions
63
-
## What are the client configuration requirements?
62
+
##Frequently asked questions
63
+
###What are the client configuration requirements?
64
64
65
65
>[!NOTE]
66
66
>For Windows clients, you must have administrator rights on the client device in order to initiate the VPN connection from the client device to Azure.
@@ -77,7 +77,7 @@ The zip file also provides the values of some of the important settings on the A
77
77
>[!INCLUDE [TLS version changes](../../includes/vpn-gateway-tls-change.md)]
78
78
>
79
79
80
-
## <aname="gwsku"></a>Which gateway SKUs support P2S VPN?
80
+
###<aname="gwsku"></a>Which gateway SKUs support P2S VPN?
@@ -87,48 +87,48 @@ The zip file also provides the values of some of the important settings on the A
87
87
>The Basic SKU does not support IKEv2 or RADIUS authentication.
88
88
>
89
89
90
-
## <aname="IKE/IPsec policies"></a>What IKE/IPsec policies are configured on VPN gateways for P2S?
90
+
###<aname="IKE/IPsec policies"></a>What IKE/IPsec policies are configured on VPN gateways for P2S?
91
91
92
92
93
93
**IKEv2**
94
94
95
95
|**Cipher**|**Integrity**|**PRF**|**DH Group**|
96
-
|---| ---| ---| --- |
97
-
|GCM_AES256 |GCM_AES256| SHA384| GROUP_24 |
98
-
|GCM_AES256 |GCM_AES256| SHA384| GROUP_14 |
99
-
|GCM_AES256 |GCM_AES256| SHA384| GROUP_ECP384 |
100
-
|GCM_AES256 |GCM_AES256| SHA384| GROUP_ECP256 |
101
-
|GCM_AES256 |GCM_AES256| SHA256| GROUP_24 |
102
-
|GCM_AES256 |GCM_AES256| SHA256| GROUP_14 |
103
-
|GCM_AES256 |GCM_AES256| SHA256| GROUP_ECP384 |
104
-
|GCM_AES256 |GCM_AES256| SHA256| GROUP_ECP256 |
105
-
|AES256 | SHA384| SHA384| GROUP_24 |
106
-
|AES256 | SHA384| SHA384| GROUP_14 |
107
-
|AES256 | SHA384| SHA384| GROUP_ECP384 |
108
-
|AES256 | SHA384| SHA384| GROUP_ECP256 |
109
-
|AES256 | SHA256| SHA256| GROUP_24 |
110
-
|AES256 | SHA256| SHA256| GROUP_14 |
111
-
|AES256 | SHA256| SHA256| GROUP_ECP384 |
112
-
|AES256 | SHA256| SHA256| GROUP_ECP256 |
113
-
|AES256 | SHA256| SHA256| GROUP_2 |
96
+
|---| ---| ---| --- |
97
+
|GCM_AES256 |GCM_AES256| SHA384| GROUP_24 |
98
+
|GCM_AES256 |GCM_AES256| SHA384| GROUP_14 |
99
+
|GCM_AES256 |GCM_AES256| SHA384| GROUP_ECP384 |
100
+
|GCM_AES256 |GCM_AES256| SHA384| GROUP_ECP256 |
101
+
|GCM_AES256 |GCM_AES256| SHA256| GROUP_24 |
102
+
|GCM_AES256 |GCM_AES256| SHA256| GROUP_14 |
103
+
|GCM_AES256 |GCM_AES256| SHA256| GROUP_ECP384 |
104
+
|GCM_AES256 |GCM_AES256| SHA256| GROUP_ECP256 |
105
+
|AES256 | SHA384| SHA384| GROUP_24 |
106
+
|AES256 | SHA384| SHA384| GROUP_14 |
107
+
|AES256 | SHA384| SHA384| GROUP_ECP384 |
108
+
|AES256 | SHA384| SHA384| GROUP_ECP256 |
109
+
|AES256 | SHA256| SHA256| GROUP_24 |
110
+
|AES256 | SHA256| SHA256| GROUP_14 |
111
+
|AES256 | SHA256| SHA256| GROUP_ECP384 |
112
+
|AES256 | SHA256| SHA256| GROUP_ECP256 |
113
+
|AES256 | SHA256| SHA256| GROUP_2 |
114
114
115
115
**IPsec**
116
116
117
117
|**Cipher**|**Integrity**|**PFS Group**|
118
-
|---| ---| ---|
119
-
|GCM_AES256| GCM_AES256 | GROUP_NONE |
120
-
|GCM_AES256| GCM_AES256 | GROUP_24 |
121
-
|GCM_AES256| GCM_AES256 | GROUP_14 |
122
-
|GCM_AES256| GCM_AES256 | GROUP_ECP384 |
123
-
|GCM_AES256| GCM_AES256 | GROUP_ECP256 |
124
-
| AES256| SHA256 | GROUP_NONE |
125
-
| AES256| SHA256 | GROUP_24 |
126
-
| AES256| SHA256 | GROUP_14 |
127
-
| AES256| SHA256 | GROUP_ECP384 |
128
-
| AES256| SHA256 | GROUP_ECP256 |
129
-
| AES256| SHA1 | GROUP_NONE |
130
-
131
-
## <aname="TLS policies"></a>What TLS policies are configured on VPN gateways for P2S?
118
+
|---| ---| ---|
119
+
|GCM_AES256| GCM_AES256 | GROUP_NONE |
120
+
|GCM_AES256| GCM_AES256 | GROUP_24 |
121
+
|GCM_AES256| GCM_AES256 | GROUP_14 |
122
+
|GCM_AES256| GCM_AES256 | GROUP_ECP384 |
123
+
|GCM_AES256| GCM_AES256 | GROUP_ECP256 |
124
+
| AES256| SHA256 | GROUP_NONE |
125
+
| AES256| SHA256 | GROUP_24 |
126
+
| AES256| SHA256 | GROUP_14 |
127
+
| AES256| SHA256 | GROUP_ECP384 |
128
+
| AES256| SHA256 | GROUP_ECP256 |
129
+
| AES256| SHA1 | GROUP_NONE |
130
+
131
+
###<aname="TLS policies"></a>What TLS policies are configured on VPN gateways for P2S?
132
132
**TLS**
133
133
134
134
|**Policies**|
@@ -146,7 +146,7 @@ The zip file also provides the values of some of the important settings on the A
146
146
|TLS_RSA_WITH_AES_128_CBC_SHA256 |
147
147
|TLS_RSA_WITH_AES_256_CBC_SHA256 |
148
148
149
-
## <aname="configure"></a>How do I configure a P2S connection?
149
+
###<aname="configure"></a>How do I configure a P2S connection?
150
150
151
151
A P2S configuration requires quite a few specific steps. The following articles contain the steps to walk you through P2S configuration, and links to configure the VPN client devices:
0 commit comments