Projects › Route-Based Site-to-Site VPN: Tunnel Interface and eBGP, with IKEv2 Design
Route-Based Site-to-Site VPN: Tunnel Interface and eBGP, with IKEv2 Design
A manufacturer is replacing a leased line to its branch with an internet VPN. Both routers are on the internet already (HQ 198.51.100.2, branch 203.0.113.2) and the ERP server is at HQ. The network team wants a route-based VPN: a tunnel interface at each end and eBGP across it, so new branch subnets are advertised instead of added to crypto ACLs on both sides. Build the tunnel and the routing in the sandbox and prove branch traffic uses it; design the IKEv2 and IPsec protection that turns the tunnel into a VPN.
Difficulty: advanced · Time: about 60 minutes
Why it matters
Route-based VPNs with a routing protocol over them are how most enterprises connect branches and clouds today. The usual faults are routing faults (traffic leaking outside the tunnel, a session sourced from the wrong address), so building and proving the routing is the job, and the crypto is a configuration you must be able to write from memory.
Technologies
- IPsec
- IKEv2
- Virtual Tunnel Interface (VTI)
- GRE
- eBGP
Related projects
- Multi-Area OSPFv2 Network with Area 0 Backbone & Stub Routing
- Branch-to-Cloud WAN Fabric Deployment via Cisco SD-WAN
- WAN-Edge QoS for Voice and Video: Classify, Queue, Apply
- Cisco SD-WAN Direct Internet Access (DIA) with Enterprise Firewall
- Dual-Circuit Branch: Floating Static Failover with a Pinned Probe Route
- DMVPN Phase 3: Hub-and-Spoke with On-Demand Spoke-to-Spoke Tunnels
- EIGRP for a Three-Store Retailer: Authenticated Peering and Stub Branches
- Small Office Internet Gateway with NAT Overload (PAT)