Table Of Contents
RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements
First Published: November 27, 2000Last Updated: July 31, 2009
The RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements feature allows the hostname of the network access server (NAS) to be specified—rather than the IP address of the NAS—in RADIUS attribute 66 (Tunnel-Client-Endpoint). This feature makes it easier for users to remember a hostname instead of a numerical IP address, and helps disguise the numerical IP address of the NAS.
Finding Feature Information
For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp. An account on Cisco.com is not required.
Prerequisites for RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements
A Cisco IOS XE platform that supports VPDN is required. See the "Glossary" section for more information about VPDN.
Restrictions for RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements
Your Cisco router must be running a Cisco IOS XE software image that supports virtual private dialup networks (VPDNs).
Information About RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements
This section includes the following concepts:
How the RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements are Used
Virtual Private Networks (VPNs) use Layer 2 Forwarding (L2F) or Layer 2 Tunnel Protocol (L2TP) tunnels to tunnel the link layer of high-level protocols (for example, PPP or asynchronous High-Level Data Link Control (HDLC)). Internet service providers (ISPs) configure their NASs to receive calls from users and forward the calls to the customer tunnel server. Usually, the ISP maintains only information about the tunnel server—the tunnel endpoint. The customer maintains the IP addresses, routing, and other user database functions of the tunnel server users. RADIUS attribute 66 provides the customer with the ability to specify the hostname of the NAS instead of the IP address of the NAS.
Note L2F is not supported on the Cisco ASR 1000 Series Aggregation Services Routers.
How to Configure RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements
There are no configuration tasks associated with support for the RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements in the Cisco IOS XE software.
Configuration Examples for RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements
This section provides the following configuration example:
Setting Up the RADIUS Profile for RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements: Example
The following example shows a configuration that allows the user to specify the hostname of the NAS using RADIUS attribute 66 (Tunnel-Client-Endpoint) in the RADIUS profile:cisco-avpair = vpdn:l2tp-cm-local-window-size=1024cisco-avpair = vpdn:l2tp-nosession-timeout=30cisco-avpair = vpdn:l2tp-cm-retransmit-retries=10cisco-avpair = vpdn:l2tp-cm-min-timeout=2cisco-avpair = vpdn:l2tp-hello-interval=60Service-Type = outboundTunnel-Assignment-Id_tag1 = ISP1Tunnel-Client-Auth-Id_tag1 = LAC1Tunnel-Client-Endpoint_tag1 = 10.0.0.2Tunnel-Medium-Type_tag1 = IPv4Tunnel-Password_tag1 = tunnel1Tunnel-Server-Auth-Id_tag1 = LNS1Tunnel-Server-Endpoint_tag1 = 10.0.0.1Tunnel-Type_tag1 = l2tp
The following sections provide references related to the RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements feature.
Related Topic Document Title
RADIUS attribute 66
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
Feature Information for RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements
Table 1 lists the release history for this feature.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp. An account on Cisco.com is not required.
Note Table 1 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.
L2F—Layer 2 Forwarding Protocol. Protocol that supports the creation of secure virtual private dialup networks over the Internet.
L2TP—Layer 2 Tunnel Protocol. Protocol that is one of the key building blocks for virtual private networks in the dial access space and is endorsed by Cisco and other internetworking industry leaders. This protocol combines the best of Cisco's Layer 2 Forwarding (L2F) protocol and Microsoft's Point-to-Point Tunneling Protocol (PPTP).
Layer 2 Forwarding Protocol—See L2F.
Layer 2 Tunnel Protocol—See L2TP.
Point-to-Point Protocol—See PPP.
PPP—Point-to-Point Protocol. Successor to SLIP that provides router-to-router and host-to-network connections over synchronous and asynchronous circuits. Whereas SLIP was designed to work with IP, PPP was designed to work with several network layer protocols, such as IP, IPX, and ARA. PPP also has built-in security mechanisms, such as CHAP and PAP. PPP relies on two protocols: LCP and NCP.
RADIUS—Remote Authentication Dial-In User Service. Database for authenticating modem and ISDN connections and for tracking connection time.
Remote Authentication Dial-In User Service—See RADIUS.
virtual private dialup network—See VPDN.
VPDN—virtual private dialup network. A system that permits dial-in networks to exist remotely to home networks, while giving the appearance of being directly connected. VPDNs use L2TP and L2F to terminate the Layer 2 and higher parts of the network connection at the L2TP network server (LNS), instead of the L2TP access concentrator (LAC).
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2000-2009 Cisco Systems, Inc. All rights reserved.