Skip to content

Commit abecf68

Browse files
committed
add to the toc
1 parent 65a149e commit abecf68

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

articles/virtual-wan/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,8 @@
4040
items:
4141
- name: Migrate to Virtual WAN
4242
href: migrate-from-hub-spoke-topology.md
43+
- name: Interconnect Virtual WANs
44+
href: virtual-wan-connectivity.md
4345
- name: Global transit network architecture
4446
href: virtual-wan-global-transit-network-architecture.md
4547
- name: SD-WAN connectivity architecture

articles/virtual-wan/virtual-wan-connectivity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: halkazwini
55
ms.author: halkazwini
66
ms.service: azure-virtual-wan
77
ms.topic: how-to
8-
ms.date: 05/07/2025
8+
ms.date: 05/08/2025
99
---
1010

1111
# Virtual WAN to Virtual WAN connectivity options
@@ -14,7 +14,7 @@ In this article, you learn about the various connection options available to con
1414

1515
## IPsec tunnels using virtual network gateways
1616

17-
In this option, you can provision a virtual network gateway in each virtual hub of your virtual WAN environment to connect virtual WANs together.
17+
In this option, you can use IPsec tunnels to connect Virtual WANs by deploying a virtual network gateway in each virtual hub withing your virtual WAN environment.
1818

1919
Because the virtual network gateway ASN is always 65515, you can't have BGP over IPsec due to BGP loop prevention mechanism as the remote virtual hub will receive routes from the source virtual hub with 65515 in the AS-PATH and BGP will drop that. Therefore, if you want to connect two different virtual WANs, the tunnels must use static routing.
2020

0 commit comments

Comments
 (0)