Peer1IX
Internet Exchange
Services

Interconnection

Internet ExchangeMicro PoPsEdge Data Centers

Network Services

Data Center to Data CenterVirtual Connectivity HubData Center to CloudCloud to CloudPeer1ix Cloud RouterPeer1ix Virtual EdgeNAT GatewayPeer1ix PortVirtual Cross Connect

Security Services

DDoS ProtectionPeer1ix FWaaSIPsec Tunnel

Cloud Interconnect

Cloudflare Network Interconnect
Locations
Network toolsAll-in-One Network ReportBGP Looking GlassRPKI ValidatorBGP Security & Hijack CheckIP WHOISAS WHOISBGP Route ExplorerASN InsightsBGP Hijacks & Route LeaksInternet Outage TrackerCountry Internet InsightsTop Domains RankingDNS LookupSubnet CalculatorWhat Is My IP
BlogAboutContact Get connected

Route-Based vs Policy-Based IPsec VPNs

· 1 min read · Peer1IX Team

Route-Based vs Policy-Based IPsec VPNs

Two ways to decide what goes into an IPsec tunnel. Why route-based designs are usually the better choice.

Policy-based VPNs

The tunnel is defined by policies listing source and destination subnets. Traffic matching those pairs is encrypted. Adding a subnet means changing the policy on both sides.

Route-based VPNs

The tunnel appears as a virtual interface. Any traffic routed to that interface is encrypted. Routing — static or dynamic — decides what goes through.

Why route-based usually wins

  • Supports BGP over the tunnel, so routes update automatically.
  • Easier to add networks without renegotiating policies.
  • Simpler failover between multiple tunnels.

When policy-based is fine

Very simple, static connections between two fixed subnets.

Peer1IX recommendation

Use route-based tunnels with BGP for connections into the Peer1IX fabric whenever your equipment supports it.

route-based VPNpolicy-based VPNdesign