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
### Does everything need to match between the Azure VPN gateway policy and my on-premises VPN device configurations?
29
-
30
-
Your on-premises VPN device configuration must match or contain the following algorithms and parameters that you specify on the Azure IPsec/IKE policy:
31
-
32
-
* IKE encryption algorithm
33
-
* IKE integrity algorithm
34
-
* DH Group
35
-
* IPsec encryption algorithm
36
-
* IPsec integrity algorithm
37
-
* PFS Group
38
-
* Traffic Selector (*)
39
-
40
-
The SA lifetimes are local specifications only. They don't need to match.
41
-
42
-
If you enable **UsePolicyBasedTrafficSelectors**, you need to ensure your VPN device has the matching traffic selectors defined with all combinations of your on-premises network (local network gateway) prefixes to/from the Azure virtual network prefixes, instead of any-to-any. For example, if your on-premises network prefixes are 10.1.0.0/16 and 10.2.0.0/16, and your virtual network prefixes are 192.168.0.0/16 and 172.16.0.0/16, you need to specify the following traffic selectors:
43
-
44
-
* 10.1.0.0/16 <====> 192.168.0.0/16
45
-
* 10.1.0.0/16 <====> 172.16.0.0/16
46
-
* 10.2.0.0/16 <====> 192.168.0.0/16
47
-
* 10.2.0.0/16 <====> 172.16.0.0/16
48
-
49
28
For more information, see [Connect multiple on-premises policy-based VPN devices](../articles/vpn-gateway/vpn-gateway-connect-multiple-policybased-rm-ps.md).
50
29
51
30
### <aname ="DH"></a>Which Diffie-Hellman Groups are supported?
52
31
53
-
The table below lists the supported Diffie-Hellman Groups for IKE (DHGroup) and IPsec (PFSGroup):
32
+
The following table lists the corresponding Diffie-Hellman groups supported by the custom policy:
0 commit comments