Guest

Preview Tool

Cisco Bug: CSCsg39216 - ezvpn tunnel traffic with acl keyword is not excluded from NAT

Last Modified

Feb 22, 2014

Products (1)

  • Cisco IOS

Known Affected Releases

12.4(6)T5

Description (partial)

Symptom: 

When EZVPN client is configured with "acl" keyword, the tunneled (vpn) traffic also gets NATed. 
This only happens if there is a NAT configuration that includes the interesting VPN traffic.  

The tunneled traffic should be bypassed from NAT when the VPN is up. 

Example: 

crypto ipsec client ezvpn hwclient
 connect auto
 group cisco key cisco123
 mode network-extension
 peer 10.1.1.1
 acl 103
 
access-list 103 permit ip 192.168.100.0 0.0.0.255 192.168.1.0 0.0.0.255


Condition: 

1) ezvpn client is configured
2) interesting tunnel traffic is defined using the "acl" keyword under global ezvpn
   configuration
3) NAT is configured
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.