NAT Interoperability Support
With the Easy VPN Client, the features automatic NAT and
access list configuration replaced any existing NAT and access list
configuration. If a tunnel timed out or dropped its connection, the NAT and
access configuration were removed automatically, preventing any Internet access
even to nontunnel destinations.
Cisco Easy VPN Remote Phase Two supports interoperability
with locally configured NAT. When the IPSec VPN tunnel is down, the router
automatically restores the previous NAT configuration. Users can continue to
access nontunnel Internet connections when the tunnel times out or
disconnects.
Local Address Support for Easy VPN Remote
Easy VPN Remote Phase Two provides an interface
configuration option, which makes it possible to specify the interface to use in
determining the IP address as the source of VPN tunnel traffic. Typically, the
loopback interface is the interface used to source tunnel traffic. The syntax is
as follows:
Rtr1(config)#crypto ipsec client ezvpn name
Rtr1(config-crypto-ezvpn)#local-address interface-id
The following example shows the local-address
subcommand used to specify the loopback0 interface for sourcing tunnel
traffic:
Rtr1#config t Rtr1(config)#crypto ipsec client ezvpn
telecom-client
Rtr1(config-crypto-ezvpn)#local-address
loopback0 Rtr1(config-crypto-ezvpn)#
Sections
Comments (0 posted)
Syndication
