Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • SD-WAN / SD-Branch Architecture for MSSPs

    Home FortiGate / FortiOS 7.4.0 SD-WAN / SD-Branch Architecture for MSSPs
    7.4.0
    7.4.0
    7.2.0
    7.0.0
    6.4.0

    Hub connection: many-to-one

    Hub connection: many-to-one

    In this example, Site 1 has two Internet connections, while the Hub has only a single one. With the BGP on loopback design, we can configure a single Dial-Up IPsec endpoint on the Hub to which the Spoke will establish two static IPsec tunnels.

    Remember that, unlike with the legacy BGP per overlay design, we no longer need to configure tunnel subnets, and this is why the same Spoke can establish multiple IPsec tunnels towards the same Dial-Up endpoint without tunnel subnet conflicts. We also do not need to configure additional BGP sessions, since there is always a single session between the Spoke and the Hub.

    The IKE exchange-ip-addrv4 feature will inject the /32 loopback route through both of the established tunnels, allowing the BGP routes to be recursively resolved through all available overlay paths.

    Previous
    Next

    Hub connection: many-to-one

    Hub connection: many-to-one

    In this example, Site 1 has two Internet connections, while the Hub has only a single one. With the BGP on loopback design, we can configure a single Dial-Up IPsec endpoint on the Hub to which the Spoke will establish two static IPsec tunnels.

    Remember that, unlike with the legacy BGP per overlay design, we no longer need to configure tunnel subnets, and this is why the same Spoke can establish multiple IPsec tunnels towards the same Dial-Up endpoint without tunnel subnet conflicts. We also do not need to configure additional BGP sessions, since there is always a single session between the Spoke and the Hub.

    The IKE exchange-ip-addrv4 feature will inject the /32 loopback route through both of the established tunnels, allowing the BGP routes to be recursively resolved through all available overlay paths.

    Previous
    Next