Connecting sites across the globe β the technologies, tunnels, and security that make it work.
WAN Technology Overview
Different services for different connectivity needs
MPLS
Type: Service provider managed
Speed: 10 Mbps β 10+ Gbps
Latency: Very low (label switching)
QoS: Yes β built-in SLAs
Uses short labels for forwarding β faster than IP route lookups. Most enterprise WAN uses MPLS.
Metro Ethernet
Type: Ethernet WAN (E-Line, E-LAN)
Speed: 1 Mbps β 10 Gbps
Latency: Low
Model: Looks like a LAN to customer
Extends Ethernet across metro areas. Customer sees Ethernet handoff, not Frame Relay.
DSL / Cable
DSL Type: ADSL/VDSL over phone lines
Cable: DOCSIS over coax
Speed: 1 β 1000 Mbps
Protocol: PPPoE (DSL)
Best effort, shared bandwidth. Often used for small branches or home offices (SOHO).
Cellular / Satellite
Cellular: 4G LTE / 5G
Satellite: GEO/LEO (Starlink)
Use case: Remote sites, backup WAN
Latency: High (GEO) / Low (LEO)
Used as backup links or for sites where other options aren't available.
WAN Topology Terms: Hub-and-Spoke (star) β central site connects to all branches. Full Mesh β every site connects to every other (most resilient, most expensive). Partial Mesh β compromise between the two.
PPPoE β Point-to-Point Protocol over Ethernet
Standard authentication method for DSL broadband
PPPoE encapsulates PPP frames within Ethernet frames, allowing ISPs to authenticate and track individual users over a shared medium. The router acts as the PPPoE client β credentials go in the dialer interface.
PPPoE Client Configuration
! Create dialer interface with PPP credentialsinterfaceDialer1ip address negotiated! ISP assigns via IPCPencapsulation pppdialer pool1ppp chap hostnamemyuser@isp.comppp chap passwordsecretpasswordip nat outside! Bind physical interface to dialer poolinterfaceGigabitEthernet0/0no ip addresspppoe-client dial-pool-number1
GRE β Generic Routing Encapsulation
RFC 2784 Β· Protocol 47 Β· Tunnels ANY packet including multicast
GRE creates a virtual point-to-point link between two routers over an IP network. Unlike IPsec, GRE supports multicast and broadcast β meaning you can run routing protocols (OSPF, EIGRP) inside the tunnel.
GRE Overhead: Each GRE packet adds 24 bytes of overhead (20-byte IP header + 4-byte GRE header). MTU issues are common β tune MSS with ip tcp adjust-mss 1436 on the tunnel interface.
GRE + IPsec: GRE is not encrypted. In production, GRE tunnels are often protected with IPsec to get the best of both: GRE supports multicast, IPsec provides encryption.
IPsec β IP Security
Suite of protocols for authenticating and encrypting IP traffic
IPsec secures traffic between two endpoints through two phases. It provides confidentiality (encryption), integrity (hashing), authentication, and anti-replay protection.
Site A
10.1.0.0/24
203.0.113.1
βββ
IKE Phase 1
ISAKMP SA
IKE Phase 2
IPsec SA (ESP)
βββ
Site B
10.2.0.0/24
203.0.113.2
IKE Phase 1
Establishes an ISAKMP SA β a secure, authenticated channel for negotiation. Uses Main Mode (6 messages) or Aggressive Mode (3 messages).
Uses the Phase 1 channel to negotiate IPsec SAs for actual data encryption. Quick Mode only (3 messages).
Creates: ESP or AH SAs for the data traffic (unidirectional)
ESP (Encapsulating Security Payload): Protocol 50. Provides encryption + authentication. Most common in site-to-site VPNs.
AH (Authentication Header): Protocol 51. Authentication + integrity only. No encryption. Rarely used β ESP supersedes it.
QoS β Quality of Service Basics
Prioritizing traffic to ensure voice and video perform well
QoS solves the bandwidth competition problem. Without it, a large file download could impair a VoIP call. The three main QoS tools: Classification, Marking, and Queuing.
DSCP (Differentiated Services Code Point): 6-bit field in the IP header. Values 0β63. Replaces the old IP Precedence (3-bit). The most common values to know:
46
EF
Voice RTP
34
AF41
Video (H.264)
24
CS3
Call Signaling
0
BE / CS0
Best Effort
Trust Boundary: Mark traffic as close to the source as possible. IP phones should mark their own traffic (DSCP 46 for voice, 26 for signaling). The first Cisco switch port is the trust boundary β re-mark or trust the device's markings here.
interfaceTunnel0descriptionGRE to Branchip address172.16.0.1 255.255.255.252tunnel sourceGigabitEthernet0/0tunnel destination203.0.113.2ip tcp adjust-mss1436
2
Configure GRE tunnel on Branch router
interfaceTunnel0descriptionGRE to HQip address172.16.0.2 255.255.255.252tunnel sourceGigabitEthernet0/0tunnel destination10.0.0.1ip tcp adjust-mss1436
3
Add a static route through the tunnel
! On HQ: route to branch LAN via tunnelip route192.168.2.0 255.255.255.0 172.16.0.2! Verifyshow interface Tunnel0ping 172.16.0.2
Lab B β Run OSPF over the GRE Tunnel
GRE supports multicast, so OSPF can run over the tunnel
1
Enable OSPF on both routers β include tunnel interface
! On HQrouter ospf1network172.16.0.0 0.0.0.3 area 0network10.1.0.0 0.0.0.255 area 0! On Branchrouter ospf1network172.16.0.0 0.0.0.3 area 0network192.168.2.0 0.0.0.255 area 0
2
Verify OSPF neighborship over tunnel
show ip ospf neighborshow ip route ospf! Should see O routes to the remote LAN