Configuring the mesh VPN topology

Last Updated : Apr 10, 2018 |
Prolog information
  1. Configure Branch Office 1 as follows:
    • The default gateway is the Internet interface
    • VPN policy is configured on the Internet interface egress as follows:
      • Traffic from the local subnets to the second spoke subnets -> encrypt, using tunnel mode IPSec, with the remote peer being the second spoke
      • Traffic from the local subnets to any IP address -> encrypt, using tunnel mode IPSec, with the remote peer being the main office (VPN hub)
    • An access control list (ACL) is configured on the Internet interface to allow only the VPN / ICMP traffic. See step 2 for configuration settings.
    ADDITIONAL INFORMATION:
    Note:
    For information about using access control lists, see Policy lists.
  2. Configure Branch Office 2 as follows:
    • The default gateway is the Internet interface
    • VPN policy is configured on the Internet interface egress as follows:
      • Traffic from the local subnets to the First Spoke subnets -> encrypt, using tunnel mode IPSec, with the remote peer being the First Spoke
      • Traffic from the local subnets to any IP address -> encrypt, using tunnel mode IPSec, with the remote peer being the Main Office (VPN hub)
    • An ACL is configured on the Internet interface to allow only the VPN / ICMP traffic. See Mesh VPN topology – Branch Office 2 for configuration settings.
    ADDITIONAL INFORMATION:
    Note:
    For information about using access control lists, see Policy lists.
  3. Configure the VPN Hub (Main Office) as follows:
    • Static routing: Branch subnets -> Internet interface
    • The VPN policy portion for the branch is configured as a mirror image of the branch, as follows:
      • Traffic from any IP address to branch local subnets -> encrypt, using tunnel mode IPSec
      • The remote peer is the VPN Spoke (Branch Internet address)