An organization deploys a client-based IPsec VPN solution for remote system administrators. During initial deployment testing, users connecting from home networks behind Network Address Translation (NAT) devices experience immediate packet drops when using IPsec with Authentication Header (AH). However, changing the VPN configuration to use Encapsulating Security Payload (ESP) resolves the issue and allows full connectivity. Which of the following best explains why the AH configuration failed in this scenario?
- Authentication Header includes the outer IP header in its Integrity Check Value calculation, causing cryptographic validation failure when NAT modifies the IP address.Answer
- BAuthentication Header relies exclusively on TCP port 500 for key negotiation, which cannot be translated by PAT routers that only perform UDP port mapping.
- CAuthentication Header encapsulates data at OSI Layer 2, preventing it from being routed across Layer 3 public network boundaries without GRE.
- DAuthentication Header encrypts authentication credentials using TACACS+ headers, which PAT gateways rewrite and corrupt during IP address overload translation.
Answer
Authentication Header (AH) includes the outer IP header in its ICV integrity calculation, causing packet drops when a NAT router modifies the source/destination IP address.
The correct answer identifies that IPsec Authentication Header (AH) includes the outer IP header in its integrity hash calculation. When a NAT router translates the IP address, the header modification invalidates the cryptographic checksum, causing the recipient IPsec endpoint to drop the packet. Switching to Encapsulating Security Payload (ESP) avoids this because ESP does not include the outer IP header in its ICV.
Step-by-Step Solution
Key Concept
IPsec AH vs ESP NAT Incompatibility