Skip to content

Commit a546a1e

Browse files
correct example IP addresses
1 parent 8f74ac6 commit a546a1e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/content/docs/magic-wan/configuration/manually/third-party/azure/azure-vpn-gateway.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -104,9 +104,9 @@ Tunnel health checks make use of ICMP probes sent from the Cloudflare side of th
104104
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.
105105

106106
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**.
110110

111111
:::note
112112
It is important to ensure the subnet selected for the Interface Address does not overlap with any other subnet.

0 commit comments

Comments
 (0)