Engineers troubleshooting a remote access IPsec IKEv2 VPN deployment notice that clients can successfully complete initial IKE negotiations over UDP port 500 when assigned a public IPv4 address directly. However, when telecommuters attempt to connect from behind residential routers performing Port Address Translation (PAT), Phase 2 negotiation fails and no encrypted data passes through the tunnel because the intermediate PAT router drops IP Protocol 50 (ESP) packets. Which configuration modification on the VPN gateway will resolve this connection issue while preserving payload encryption for telecommuters?
- Enable NAT Traversal (NAT-T) on the gateway to encapsulate IPsec ESP packets inside UDP port 4500 datagrams.Answer
- BSwitch the IPsec security protocol from Encapsulating Security Payload (ESP) to Authentication Header (AH) operating in transport mode.
- CReconfigure the IKE negotiation parameters on the gateway to transmit key exchange traffic over TCP port 500 instead of UDP port 500.
- DRebind the IPsec VPN service port to listen for raw ESP packet encapsulation over TCP port 443.
Answer
Enable NAT Traversal (NAT-T) on the gateway to encapsulate IPsec ESP packets inside UDP port 4500 datagrams.
Enabling NAT Traversal (NAT-T) dynamically detects intermediate NAT/PAT devices during IKE negotiations. Upon detection, the gateway and client encapsulate IPsec ESP packets (IP Protocol 50) within UDP datagrams using destination port 4500. Because UDP port 4500 includes standard Layer 4 port headers, intermediate routers performing Port Address Translation (PAT) can translate and forward the traffic without dropping the VPN connection or invalidating payload encryption.
Step-by-Step Solution
Key Concept
IPsec NAT Traversal (NAT-T) and UDP Port 4500 Encapsulation