Table Of Contents
Prerequisites for L2TP Domain Screening
Information About L2TP Domain Screening
How to Configure L2TP Domain Screening
Configuring L2TP Domain Screening with Global Preauthentication
Configuring a RADIUS User Profile for L2TP Domain Screening with Global Preauthentication
Configuring L2TP Domain Screening with Per-VPDN Group Preauthentication
Configuration Examples for L2TP Domain Screening
L2TP Domain Screening with Global Preauthentication: Example
L2TP Domain Screening with Per-VPDN Group Preauthentication: Example
L2TP Domain Screening
The Layer 2 Tunnel Protocol (L2TP) Domain Screening feature provides a flexible mechanism for controlling session access to an L2TP tunnel. This feature provides the ability to modify the domain portion of the username seamlessly when a subscriber enters into a virtual private network (VPN) service. The L2TP Domain Screening feature allows per-user L2TP tunnel setup by combining the following two features:
•
User preauthentication using the vpdn authen-before-forward command
•
Modifying the domain portion of the username using the vpn service command to bind an incoming session to a certain L2TP tunnel
These two commands work together in the L2TP Domain Screening feature to make sure that the appropriate domain has been screened before access is allowed to an L2TP tunnel for the user session.
History for the L2TP Domain Screening Feature
Release Modification12.3(7)XI7
This feature was introduced on the Cisco 10000 series router.
12.2(31)SB2
This feature was integrated into Cisco IOS Release 12.2(31)SB2.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for L2TP Domain Screening
•
Information About L2TP Domain Screening
•
How to Configure L2TP Domain Screening
•
Configuration Examples for L2TP Domain Screening
Prerequisites for L2TP Domain Screening
Before enabling L2TP Domain Screening, you must configure the L2TP access concentrator (LAC) to request authentication of a complete username before making a forwarding decision for dial-in L2TP. In other words, the LAC preauthenticates username@domain to find the correct L2TP tunnel for the user session.
You can configure virtual private dial-up network (VPDN) preauthentication to occur globally or per VPDN group. For global VPDN preauthentication, authentication and authorization should be done using an authentication server. For per-VPDN group-level preauthentication, authentication and authorization should be done locally.
Information About L2TP Domain Screening
To configure the L2TP Domain Screening feature, you should understand the following concept:
•
L2TP tunnel authentication
L2TP Tunnel Authentication
Figure 1 shows the general process flow for tunnel authentication. In this case, the vpdn authen-before-foreward process is called if necessary to authenticate the username and domain name to find the correct L2TP tunnel for the session. If no authentication is required, the tunnel match for the domain name is found for the session. In either case, the original username with the original domain is used for session authentication at the L2TP network server.
Figure 1 Normal Tunnel Authentication Without VPN Service
In Figure 2, the same authentication flow proceeds, this time with the VPN service applied to the configuration. Just as before, if the vpdn authen-before-foreward process determines that the session must be locally authenticated before being placed into the correct tunnel, authentication proceeds as normal. However, with the vpn service statement applied, the session is placed into the appropriate tunnel for the VPN domain.
Figure 2 Normal Tunnel Authentication with VPN Service Configured
Figure 3 shows the full VPN service application flow. If local authentication at the LAC is required and a VPN service is configured, a local authentication is done with the username provided and the domain of the VPN service provider. This step returns the necessary L2TP tunnel for this VPN session. If VPN service is not configured, local authentication is provided on the username and domain name provided by the subscriber.
If the session does not require local authentication but there is a configured VPN service, the session is placed into the L2TP tunnel for the VPN service provider. Otherwise, the session will be placed into the tunnel for the specified domain name.
In any of these scenarios, the username and domain name for the subscriber session stay the same at the L2TP network server (LNS). This allows a wholesale provider to dedicate a service provider for providing all VPN services to its subscribers without the need for complex configuration for each VPN.
The vpn service command binds a physical incoming interface to a certain tunnel. The result is that no matter what username or domain is presented, the user is always forwarded to the specified tunnel configured by the vpn service command.
Figure 3 New Operation with VPN Service
How to Configure L2TP Domain Screening
To configure L2TP Domain Screening, enable VPN service and VPDN preauthentication on the LAC. You can enable VPDN preauthentication globally or for specific VPDN groups.
This section contains the following procedures:
•
Configuring L2TP Domain Screening with Global Preauthentication (required)
•
Configuring a RADIUS User Profile for L2TP Domain Screening with Global Preauthentication (required)
•
Configuring L2TP Domain Screening with Per-VPDN Group Preauthentication (required)
Configuring L2TP Domain Screening with Global Preauthentication
To configure L2TP Domain Screening with global pre-authentication, enable VPN service and enable VPDN pre-authorization globally. RADIUS authentication and authorization are required for per-user tunnels.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
aaa new-model
4.
aaa authentication ppp {default | list-name] method1 [method2...]
5.
aaa authorization {network | exec | commands level | reverse-access | configuration} {default | list-name} method1 [method2...]
6.
radius-server host {hostname | ip-address} [auth-port port-number] [acct-port port-number]
7.
radius-server key {0 string | 7 string | string}
8.
vpdn enable
9.
vpdn authen-before-forward
10.
interface atm interface-number
11.
ip address ip-address mask
12.
pvc vpi/vci
13.
encapsulation aal5snap
14.
protocol pppoe
15.
vpn service domain-name [replace-authen-domain]
16.
end
DETAILED STEPS
Configuring a RADIUS User Profile for L2TP Domain Screening with Global Preauthentication
Global preauthentication for L2TP domain screening requires RADIUS authentication and authorization. Each user must have a RADIUS user profile that enables per-user L2TP tunneling.
The following example shows a user profile for user_1@xnet.net; the IP address in the profile is the LNS interface connected to the LAC.
[ /Radius/UserLists/Default/user_1@xnet.net ]
Name = user_1@xnet.net
Description = TEST
Password = <encrypted>
Enabled = TRUE
cisco-avpair = vpdn:tunnel-type=l2tp
cisco-avpair = vpdn:l2tp-tunnel-password=tunnel
cisco-avpair = vpdn:l2tp-hello-interval=60
cisco-avpair = vpdn:ip-addresses=103.1.1.1
cisco-avpair = vpdn:tunnel-id=LAC1-1
Framed-protocol = PPP
Service-Type = Outbound
Configuring L2TP Domain Screening with Per-VPDN Group Preauthentication
To configure L2TP Domain Screening with per-VPDN group preauthentication, enable VPN service and enable VPDN preauthentication by specific VPDN group.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
aaa new-model
4.
aaa authentication ppp {default | list-name} method1 [method2...]
5.
aaa authorization {network | exec | commands level | reverse-access | configuration} {default | list-name} method1 [method2...]
6.
vpdn enable
7.
vpdn-group name
8.
request-dialin
9.
protocol l2tp
10.
domain domain-name
11.
exit
12.
authen-before-forward
13.
initiate-to ip ip-address
14.
end
15.
configure terminal
16.
interface atm interface-number
17.
ip address ip-address mask
18.
pvc vpi/vci
19.
encapsulation aal5snap
20.
protocol pppoe
21.
vpn service domain-name [replace-authen-domain]
22.
end
DETAILED STEPS
Configuration Examples for L2TP Domain Screening
This section provides the following configuration examples:
•
L2TP Domain Screening with Global Preauthentication: Example
•
L2TP Domain Screening with Per-VPDN Group Preauthentication: Example
L2TP Domain Screening with Global Preauthentication: Example
The following partial sample configuration shows the L2TP Domain Screening feature with global preauthentication.
Router# show running-config!...hostname esr1_client...aaa new-model!aaa authentication login mylist enable lineaaa authentication ppp default group radiusaaa authorization network default group radius!aaa nas port extendedaaa session-id commonip subnet-zerono ip gratuitous-arpsip host zeppelin-2 1.0.0.253!vpdn enablevpdn authen-before-forwardvpdn ip udp ignore checksumvpdn search-order domain!vpdn-group 1accept-dialinprotocol pppoevirtual-template 1pppoe limit per-mac 2pppoe limit per-vc 2pppoe limit per-vlan 2pppoe limit max-sessions 2!ppp hold-queue 8000no virtual-template snmp!...!interface Loopback1no ip address!interface FastEthernet0/0/0ip address 23.5.11.7 255.255.0.0speed 100full-duplexhold-queue 4096 inhold-queue 4096 out!interface GigabitEthernet1/0/0no ip addressnegotiation auto!!interface ATM4/0/0.101 multipointatm pppatm passiverange pvc 52/101 52/101encapsulation aal5autoppp Virtual-Template1!pvc-in-range 52/101vpn service znet.net1 replace-authen-domain!!interface ATM5/0/0no ip addressno ip mroute-cacheno atm pxf queuingatm clock INTERNALno atm auto-configurationno atm ilmi-keepaliveno atm address-registrationno atm ilmi-enable!interface ATM5/0/0.101 multipointatm pppatm passiverange pvc 51/101 51/101encapsulation aal5autoppp Virtual-Template1!pvc-in-range 51/101vpn service znet.net1 replace-authen-domain!!...radius-server attribute nas-port format dradius-server host 23.5.6.100 auth-port 1645 acct-port 1646radius-server retransmit 4radius-server timeout 15radius-server key cisco!control-plane!call admission limit 90!...!endL2TP Domain Screening with Per-VPDN Group Preauthentication: Example
The following partial sample configuration shows the L2TP Domain Screening feature with per-VPDN group preauthentication.
Router# show running-config!...hostname esr1_client...aaa new-model!!aaa authentication login mylist enable lineaaa authentication ppp default localaaa authorization network default local!aaa nas port extendedaaa session-id commonip subnet-zerono ip gratuitous-arpsip host zeppelin-2 1.0.0.253!!vpdn enablevpdn ip udp ignore checksumvpdn search-order domain!vpdn-group 1accept-dialinprotocol pppoevirtual-template 1pppoe limit per-mac 2pppoe limit per-vc 2pppoe limit per-vlan 2pppoe limit max-sessions 2!!vpdn-group LAC_1request-dialinprotocol l2tpdomain znet.net1initiate-to ip 103.1.1.1local name LAC1-1authen-before-forwardl2tp tunnel password 0 tunnel!ppp hold-queue 8000no virtual-template snmpusername LAC1-1 nopasswordusername LNS1-1 nopasswordusername user_1_1@znet.net1 password 0 sanfran_1_1...!interface ATM4/0/0.101 multipointatm pppatm passiverange pvc 52/101 52/101encapsulation aal5autoppp Virtual-Template1!pvc-in-range 52/101vpn service znet.net1 replace-authen-domain!!interface ATM5/0/0no ip addressno ip mroute-cacheno atm pxf queuingatm clock INTERNALno atm auto-configurationno atm ilmi-keepaliveno atm address-registrationno atm ilmi-enable!interface ATM5/0/0.101 multipointatm pppatm passiverange pvc 51/101 51/101encapsulation aal5autoppp Virtual-Template1!pvc-in-range 51/101vpn service znet.net1 replace-authen-domain!...radius-server attribute nas-port format d!control-plane!call admission limit 90!...endAdditional References
The following sections provide references related to the L2TP Domain Screening feature.
Related Documents
Standards
Standard TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFC TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Command Reference
This section documents modified commands only.
vpn service
To configure a static domain name, use the vpn service command in ATM VC, ATM VC class or VC class configuration mode or in PVC range configuration mode. To remove a static domain name, use the no form of this command.
vpn service domain-name [replace-authen-domain]
no vpn service domain-name [replace-authen-domain]
Syntax Description
Defaults
No default behavior or values
Command Modes
ATM VC configuration
ATM VC class configuration
PVC range configurationCommand History
Usage Guidelines
Use the vpn service command in a permanent virtual circuit (PVC), VC class configuration, or PVC range configuration so that PPP over ATM (PPPoA) or PPP over Ethernet over ATM (PPPoEoA) sessions in those PVCs will be forwarded according to the domain name supplied, without starting PPP.
To replace the VPN service domain name with the domain name from the username during preauthentication, use this command with the replace-authen-domain keyword, in conjunction with the vpdn authen-before-forward command.
Examples
In the following partial example, VPDN group 1 is selected for PPPoA session forwarding based on the domain name example.com:
vpdn-group 1request-dialinprotocol l2tpdomain example.cominitiate-to ip 10.1.1.1 priority 1...interface ATM1/0.1 multipointpvc 101encapsulation aal5mux ppp virtual-Template 1vpn service example.netIn the following partial example using the replace-authen-domain keyword, the domain field is replaced by the domain name during preauthentication:
vpdn-group 1request-dialinprotocol l2tpdomain example.netauthen-before-forwardinitiate-to ip 10.1.1.1 priority 1...interface atm 4/0ip address 3.0.0.2 255.255.0.0pvc 1/20encapsulation aal5mux ppp virtual-Template 1vpn service example.net replace-authen-domainRelated Commands
Command Descriptionvpdn authen-before-forward
Enables authentication of all dial-in L2TP sessions before the sessions are forwarded to the tunnel server (global preauthentication).
Glossary
L2TP—Layer 2 Tunnel Protocol. An Internet Engineering Task Force (IETF) standards track protocol defined in RFC 2661 that provides tunneling of PPP. Based upon the best features of L2F (Layer 2 Forwarding Protocol) and PPTP (Point-to-Point Tunneling Protocol), L2TP provides an industry-wide interoperable method of implementing VPDN.
LNS—L2TP network server. A node that acts as one side of an L2TP tunnel endpoint and is a peer to the L2TP access concentrator (LAC). The LNS is the logical termination point of a PPP session that is being tunneled from the remote system by the LAC. Analogous to the Layer 2 Forwarding (L2F) home gateway (HGW).
LAC—L2TP access concentrator. A node that acts as one side of an L2TP tunnel endpoint and is a peer to the L2TP network server (LNS). The LAC sits between an LNS and a remote system and forwards packets to and from each. Packets sent from the LAC to the LNS require tunneling with the L2TP protocol. The connection from the LAC to the remote system is either local or a PPP link.
NAS—Network access server. Cisco platform (or collection of platforms, such as an AccessPath system) that interfaces between the packet world (for example, the Internet) and the circuit world (for example, the public switched telephone network (PSTN)).
VPDN—Virtual private dial-up network. Also known as virtual private dial network. A VPDN is a network that extends remote access to a private network using a shared infrastructure. VPDNs use Layer 2 tunnel technologies (L2F, L2TP, and PPTP) to extend the Layer 2 and higher parts of the network connection from a remote user across an internet service provider (ISP) network to a private network. VPDNs are a cost effective method of establishing a long-distance, point-to-point connection between remote dial users and a private network.
VPN—Virtual private network. Enables IP traffic to travel securely over a public TCP/IP network by encrypting all traffic from one network to another. A VPN uses "tunneling" to encrypt all information at the IP level.
Note
See Internetworking Terms and Acronyms for terms not included in this glossary.
Copyright © 2005 Cisco Systems, Inc. All rights reserved.





