How to build dual WAN site to site VPN tunnel
Branch office won’t lost access if headquarter primary WAN is dead
Setting
In Headquarter:
Phase1:
My Address: 0.0.0.0
Peer Address: Dynamic Address
Phase2:
Application Scenario: Remote Access (Server Role)
Select server role will force Headquarter respond negotiation only. It is helpful to decrease headquarter loading.
Local Policy: 192.168.0.0/16
In Branch:
Phase1:
My Address: 0.0.0.0
Peer Address: Primary 192.168.168.35, Secondary 192.168.169.35
Select “Fall back to Primary Peer Gateway when possible”
Phase2:
Application Scenario: Remote Access (Client Role)
Select server role will force Headquarter respond negotiation only. It is helpful to decrease headquarter loading.
Local Policy: 10.0.0.0/8
Remote Policy:192.168.0.0/16
Test
Secondary line will take over when Primary is dead.
Then back to Primary when it backs
Note:
To ensure the Tunnel works as expected, we recommend that each Peer uses a single profile and avoids configuring multiple profiles for one Peer.
Categories
- All Categories
- 394 Beta Program
- 2.1K Nebula
- 117 Nebula Ideas
- 81 Nebula Status and Incidents
- 5.1K Security
- 82 USG FLEX H Series
- 247 Security Ideas
- 1.3K Switch
- 69 Switch Ideas
- 914 WirelessLAN
- 34 WLAN Ideas
- 5.9K Consumer Product
- 209 Service & License
- 337 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 2K FAQ
- 908 Nebula FAQ
- 415 Security FAQ
- 236 Switch FAQ
- 207 WirelessLAN FAQ
- 46 Consumer Product FAQ
- 138 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 73 About Community
- 62 Security Highlight