Skip to content

Commit ceb3bbd

Browse files
Merge pull request #268334 from aimee-littleton/patch-190
Update nat-gateway-snat.md
2 parents 95d01f6 + ce77058 commit ceb3bbd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/nat-gateway/nat-gateway-snat.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ NAT gateway selects a SNAT port at random out of the available inventory of port
4444

4545
A SNAT port can be reused to connect to the same destination endpoint. Before the port is reused, NAT gateway places a SNAT port reuse timer for cool down on the port after the connection closes.
4646

47-
The SNAT port reuse down timer helps prevent ports from being selected too quickly for connecting to the same destination. This process is helpful when destination endpoints have firewalls or other services configured that place a cool down timer on source ports. A SNAT port may be placed on a different length port reuse timer for cool down depending on how the previous connection closed. To learn more, see [Port Reuse Timers](/azure/nat-gateway/nat-gateway-resource#timers).
47+
The SNAT port reuse timer helps prevent ports from being selected too quickly for connecting to the same destination. This process is helpful when destination endpoints have firewalls or other services configured that place a cool down timer on source ports. SNAT port reuse timers vary based on how a connection flow was closed. To learn more, see [Port Reuse Timers](/azure/nat-gateway/nat-gateway-resource#timers).
4848

4949
## Example SNAT flows for NAT gateway
5050

@@ -96,4 +96,4 @@ Don't take a dependency on the specific way source ports are assigned in the abo
9696

9797
- [Design virtual network with NAT gateway](/azure/nat-gateway/nat-gateway-resource)
9898

99-
- [Azure NAT Gateway metrics and alerts](/azure/nat-gateway/nat-metrics)
99+
- [Azure NAT Gateway metrics and alerts](/azure/nat-gateway/nat-metrics)

0 commit comments

Comments
 (0)