Cisco Cisco IOS Software Release 12.2(4)YH
6
Release Notes for the SOHO 70 Series Routers and the Cisco 800 Series Routers for Cisco IOS Release 12.2(4)YH
Important Notes
TACACS+
SOHO 71 routers support the Terminal Access Controller Access Control System Plus (TACACS+)
protocol through Telnet. TACACS+ is a Cisco proprietary authentication protocol that provides remote
access authentication and related network security services, such as event logging. User passwords are
administered in a central database rather than in individual routers. TACACS+ also provides support for
separate modular authentication, authorization, and accounting (AAA) facilities that are configured at
individual routers.
protocol through Telnet. TACACS+ is a Cisco proprietary authentication protocol that provides remote
access authentication and related network security services, such as event logging. User passwords are
administered in a central database rather than in individual routers. TACACS+ also provides support for
separate modular authentication, authorization, and accounting (AAA) facilities that are configured at
individual routers.
Refer to the Cisco 806 Software Configuration Guide for more information on TACACS+. A
configuration overview is provided at the following URL:
configuration overview is provided at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/806/806swcg/routconf.htm
New Software Features in Release 12.2 T
For information regarding the features supported in Cisco IOS Release 12.2 T, refer to the
Cross-Platform Release Notes and New Feature Documentation links at the following location on
Cisco.com and the Documentation CD-ROM:
Cross-Platform Release Notes and New Feature Documentation links at the following location on
Cisco.com and the Documentation CD-ROM:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/index.htm
This URL is subject to change without notice. If it changes, point your web browser to Cisco.com, and
click on the following path:
click on the following path:
Service & Support: Technical Documents: Release 12.2 (from the Cisco IOS Software
drop-down list)
drop-down list)
Important Notes
The following sections contain important notes about Cisco IOS Release 12.2(4)YH that can apply to
SOHO 70 and Cisco 800 series routers. (Also, see the
SOHO 70 and Cisco 800 series routers. (Also, see the
Changing IP Addresses When Using the Cisco Easy VPN Client Feature
In Cisco 800 series routers, the Ethernet 0 LAN interface defaults to the primary IP address of 10.10.10.0
in a private network. If you need to change this IP address to match the local network configuration, you
can use the command ip address or the Cisco Router Web Setup (CRWS) web interface.
in a private network. If you need to change this IP address to match the local network configuration, you
can use the command ip address or the Cisco Router Web Setup (CRWS) web interface.
Using the CRWS interface to change the IP address preserves the existing IP address as the primary
address of the interface and assigns the new IP address as the secondary address on the interface. This
CRWS interface functionality maintains (does not break) the existing connection between the PC web
browser and the Cisco 800 series router and thereby does not interfere with normal router operations for
most configurations.
address of the interface and assigns the new IP address as the secondary address on the interface. This
CRWS interface functionality maintains (does not break) the existing connection between the PC web
browser and the Cisco 800 series router and thereby does not interfere with normal router operations for
most configurations.
Because of this behavior, the Cisco Easy VPN client feature assumes that if a secondary IP address exists
on the Ethernet 0 interface, the secondary address should be used as the IP address for the inside interface
for the NAT/PAT configuration. If no secondary address exists, the primary IP address will be used for
the inside interface address, as is normally done on other platforms. If this behavior is not desired, use
the ip address CLI command instead of the CRWS web interface to change the interface address.
on the Ethernet 0 interface, the secondary address should be used as the IP address for the inside interface
for the NAT/PAT configuration. If no secondary address exists, the primary IP address will be used for
the inside interface address, as is normally done on other platforms. If this behavior is not desired, use
the ip address CLI command instead of the CRWS web interface to change the interface address.