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/nat-overview.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,10 @@ titleSuffix: Azure VPN Gateway
4
4
description: Learn about NAT (Network Address Translation) in Azure VPN to connect networks with overlapping address spaces.
5
5
author: cherylmc
6
6
ms.service: vpn-gateway
7
-
ms.topic: article
7
+
ms.topic: conceptual
8
8
ms.date: 05/11/2022
9
9
ms.author: cherylmc
10
-
10
+
ms.custom: template-concept
11
11
---
12
12
# About NAT on Azure VPN Gateway
13
13
@@ -52,9 +52,9 @@ Each NAT rule defines an address mapping or translating relationship for the cor
52
52
53
53
For each NAT rule, the following two fields specify the address spaces before and after the translation:
54
54
55
-
***Internal Mappings**: This is the address space **before** the translation. For an ingress rule, this field corresponds to the original address space of the on-premises network. For an egress rule, this is the original VNet address space.
55
+
***Internal Mappings**: The address space **before** the translation. For an ingress rule, this field corresponds to the original address space of the on-premises network. For an egress rule, this is the original VNet address space.
56
56
57
-
***External Mappings**: This is the address space **after** the translation for on-premises networks (ingress) or VNet (egress). For different networks connected to an Azure VPN gateway, the address spaces for all **External Mappings** must not overlap with each other and with the networks connected without NAT.
57
+
***External Mappings**: The address space **after** the translation for on-premises networks (ingress) or VNet (egress). For different networks connected to an Azure VPN gateway, the address spaces for all **External Mappings** must not overlap with each other and with the networks connected without NAT.
Copy file name to clipboardExpand all lines: includes/vpn-gateway-faq-nat-include.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ You can create up to 100 NAT rules (Ingress and Egress rules combined) on a VPN
19
19
20
20
### Can I use / in a NAT rule name?
21
21
22
-
No. You will receive an error.
22
+
No. You'll receive an error.
23
23
24
24
### Is NAT applied to all connections on a VPN gateway?
25
25
@@ -70,7 +70,7 @@ You can use any suitable IP range that you want for External Mapping, including
70
70
71
71
### Can I use different EgressSNAT rules to translate my VNet address space to different prefixes to different on-premises networks?
72
72
73
-
Yes, you can create multiple EgressSNAT rules for the same VNet address space, and apply the EgressSNAT rules to different connections. For the connections without an EgressSNAT rule,
73
+
Yes, you can create multiple EgressSNAT rules for the same VNet address space, and apply the EgressSNAT rules to different connections.
74
74
75
75
### Can I use the same IngressSNAT rule on different connections?
76
76
@@ -80,6 +80,6 @@ Yes, this is typically used when the connections are for the same on-premises ne
80
80
81
81
You need both Ingress and Egress rules on the same connection when the on-premises network address space overlaps with the VNet address space. If the VNet address space is unique among all connected networks, you don't need the EgressSNAT rule on those connections. You can use the Ingress rules to avoid address overlap among the on-premises networks.
82
82
83
-
### What do I choose as "IP configuration ID"?
83
+
### What do I choose as "IP configuration ID"?
84
84
85
-
"IP configuration ID" is simply the name of the IP configuration object you want the NAT rule to use. With this setting, you are simply choosing which gateway public IP address applies to the NAT rule. If you haven't specified any custom name at gateway creation time, the gateway's primary IP address is assigned to the "default" IPconfiguration and the secondary IP is assigned to the "activeActive" IPconfiguration.
85
+
"IP configuration ID" is simply the name of the IP configuration object you want the NAT rule to use. With this setting, you're simply choosing which gateway public IP address applies to the NAT rule. If you haven't specified any custom name at gateway creation time, the gateway's primary IP address is assigned to the "default" IPconfiguration, and the secondary IP is assigned to the "activeActive" IPconfiguration.
0 commit comments