Skip to content

Commit ca41f15

Browse files
Merge pull request #307360 from vishalme/patch-25
Update VPN gateway user-defined routes warning
2 parents 91cc4a8 + f2255b8 commit ca41f15

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

includes/vpn-gateway-gwudr-warning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,6 @@
99
ms.author: cherylmc
1010
ms.custom: include file
1111
---
12-
* User-defined routes with a 0.0.0.0/0 destination and network security groups (NSGs) on the gateway subnet *are not supported*. Gateways with this configuration are blocked from being created. Gateways require access to the management controllers in order to function properly. [Border Gateway Protocol (BGP) route propagation](/azure/virtual-network/virtual-networks-udr-overview#border-gateway-protocol) should be enabled on the gateway subnet to ensure availability of the gateway. If BGP route propagation is disabled, the gateway won't function.
12+
* User-defined routes with a 0.0.0.0/0 destination and network security groups (NSGs) on the gateway subnet *are not supported*. User-defined routes, containing GatewaySubnet address space, with next-hop set to none or with next-hop set to NVA (which has policy to drop the traffic) are not supported. Gateways with this configuration are blocked from being created. Gateways require access to the management controllers in order to function properly. [Border Gateway Protocol (BGP) route propagation](/azure/virtual-network/virtual-networks-udr-overview#border-gateway-protocol) should be enabled on the gateway subnet to ensure availability of the gateway. If BGP route propagation is disabled, the gateway won't function.
1313

1414
* Diagnostics, data path, and control path can be affected if a user-defined route overlaps with the gateway subnet range or the gateway public IP range.

0 commit comments

Comments
 (0)