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: src/content/docs/magic-wan/configuration/manually/third-party/azure/azure-vpn-gateway.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,9 +104,9 @@ Tunnel health checks make use of ICMP probes sent from the Cloudflare side of th
104
104
Cloudflare recommends customers select a unique `/31` subnet ([RFC 1918 - Address Allocation for Private Internets](https://datatracker.ietf.org/doc/html/rfc1918)) for each IPsec tunnel which is treated as a Point-to-Point Link and provides the ideal addressing scheme to satisfy both requirements.
105
105
106
106
Example:
107
-
- Select 169.254.251.137/31 as your unique point-to-point link subnet.
108
-
- In the Cloudflare dashboard, set `169.254.251.137/31` as your tunnel's **IPv4 Interface address** (refer to [Configure Magic WAN](#configure-magic-wan)).
109
-
- In the Azure portal, add `169.254.251.137/32` to your Local Network Gateway's **Address space**.
107
+
- Select 10.252.3.55/31 as your unique point-to-point link subnet.
108
+
- In the Cloudflare dashboard, set `10.252.3.55/31` as your tunnel's **IPv4 Interface address** (refer to [Configure Magic WAN](#configure-magic-wan)).
109
+
- In the Azure portal, add `10.252.3.55/32` to your Local Network Gateway's **Address space**.
110
110
111
111
:::note
112
112
It is important to ensure the subnet selected for the Interface Address does not overlap with any other subnet.
0 commit comments