Cisco Cisco IOS Software Release 12.2(8)YJ

This section describes unexpected behavior that is fixed in Release 12.2(8)YJ.

Manual tunnel control.

The tunnel is “stuck” with minimum timers and traffic after one day.

When an Easy VPN tunnel is down, users lose Internet connectivity. Release 12.2(8)YJ prevents this loss 
of Internet connectivity by saving any existing Internet Access NAT configurations during tunnel 
creation and then restoring them when the tunnel goes down.

Telnet console supported for “xauth” prompting.

Show technical support for the Easy VPN feature.

Previously, Cisco IOS software performed the prepending and selective deletion of imported attributes 
so that DNS and WINS attributes could be set up correctly in the DHCP Server, regardless of whether a 
tunnel was up or down. The router now acts as a Proxy DNS server. Therefore, when a tunnel is down, 
use your Internet Service Provider (ISP) domain name system (DNS) to resolve DNS requests and when 
a tunnel is up, use your site DNS to resolve DNS requests.

When the router now acts as a Proxy DNS server, the router receives DNS queries on behalf of the real 
DNS servers and proxy for the users connected to the LAN. This functionality enables the DHCP server 
to immediately send out its LAN address as the DNS server IP address. The router forwards DNS queries 
from local users to real DNS servers after the WAN connection comes up and caches the DNS records 
supplied with the answers from the real DNS servers.

Currently the Easy VPN feature assumes that the remote network resides on fast ethernet 0 interface. 
Since 1700 platform has many different wics, this is a big restriction for customers. This feature adds a 
command which allows the network administrator to specify, which interfaces will have remote users 
when they configure the Easy VPN profile. 

PIX interoperability problems.