Table Of Contents
SSG Service Logon Enhancements
Information About the SSG Enhancements to SSG-SESM Interactions and Service Logon
CHAP Authentication for Proxy Services
CHAP Authentication for Tunnel Services
Attribute Filter for Service Logon
Network-Address-Translated IP in Service Logon Response
SSG Error Codes in Access Responses
SSG Service Logon Enhancements
This document describes the following Service Selection Gateway (SSG) enhancements:
•
Enhancements to SSG service logon, including CHAP authentication for L2TP tunnel and proxy services, and support for the using the Mobile Station ISDN number (MSISDN) during authentication
•
Support for additional error codes in the SSG response to the SESM
Feature History for the SSG Enhancments to SSG-SESM Interactions and Service Logon
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
•
Information About the SSG Enhancements to SSG-SESM Interactions and Service Logon
Information About the SSG Enhancements to SSG-SESM Interactions and Service Logon
This section contains the following concepts:
•
SSG Error Codes in Access Responses
•
SSG Error Codes in Access Responses
Service Logon Enhancements
When a host wants to log on to a service, SESM sends SSG a service logon request. This request is sent as a RADIUS Access-Request message that includes the SSG Command Code VSA (value 11). The host is identified by the SSG Account-Info VSA for the subscriber IP, which contains the subscriber IP address (or the port-bundle when the port-map feature is enabled). The service is indicated by the service name included in the Command Code VSA.
The following sections describe enhancements to the service logon process:
•
CHAP Authentication for Proxy Services
•
CHAP Authentication for Tunnel Services
•
Attribute Filter for Service Logon
•
Network-Address-Translated IP in Service Logon Response
CHAP Authentication for Proxy Services
This enhancement provides support for CHAP authentication for service logon requests from the SESM. SSG receives the following CHAP information in the RADIUS Access-Request message for service logon:
•
Username in attribute 1
•
CHAP ID and Response as CHAP password, attribute 3
•
CHAP challenge in either attribute 60 or the request authenticator
These parameters are sent to the authentication, authorization, and accounting (AAA) server in the Access-Request message for user authentication. The service name is added to the username if the service has been configured to use the full username (Service-Info VSA X).
Authentication using CHAP is also supported for autologon to proxy services. If the user authentication is CHAP-based and no username or password is configured for the autologon service, the CHAP information used during account logon is also used for service logon to the proxy service.
CHAP Authentication for Tunnel Services
This enhancement extends CHAP authentication to tunnel services by supporting L2TP Proxy Authentication attribute-value pairs (AVPs). The CHAP authentication information used for service logon is sent to the L2TP Network Server (LNS) in the Incoming-Call-Connected (ICCN) message. Table 1 describes the attributes that provide CHAP authentication information in ICCN messages.
For detailed information about the attributes listed in Table 1, refer to RFC 2661.
Note
The SSG server sends the CHAP challenge and response in the Cisco fixed challenge AVPs. The Cisco AVPs for fixed challenge work with PPP renegotiations between the L2TP Access Concentrator (LAC), such as SSG, and the LNS. But the CHAP parameters sent in proxy authentication AVPs are used only once. Therefore, authentication could fail if renegotiations occur between the LAC and the LNS and the LNS does not support the Cisco fixed challenge AVP.
MSISDN for Service Logon
This enhancement supports using the MSISDN for proxy and L2TP tunnel service authentication. The MSISDN for service logon can be different from the one used for account logon. This MSISDN is sent as Calling Station ID (attribute 31) in the connection RADIUS messages for proxy services to the remote AAA server. The MSISDN in the service logon request can determine the MSISDN used during service authentication.
Table 2 lists the attributes used for service logon with and without the MSISDN.
Table 2 Service Logon Comparison (With and Without MSISDN)
Service Logon Connection Authentication1 Connection Accounting to Local AAA Connection Accounting to Remote AAA2 Prepaid (Re)authorization Prepaid AccountingWithout MSISDN
Host Calling ID
Host Calling ID
Host Calling ID
Host Calling ID
Host Calling ID
With MSISDN3
Connection Calling ID
Host Calling ID
Connection Calling ID
Host Calling ID
Host Calling ID
1 Calling Station ID in RADIUS (attribute 31) in authentication for proxy services or calling number AVP (22) for L2TP tunnel services.
2 Only for proxy services.
3 Service profile is not set to filter MSISDN.
Attribute Filter for Service Logon
Some services require the MSISDN to be hidden from the service provider. To support this capability, an attribute filter can be added to the service profile. You can specify the attributes to be filtered from authentication and accounting records sent to the remote AAA server.
The SSG Service-Info VSA lists the RADIUS attributes to filter from user authentication for the service; this capability applies to both proxy RADIUS service and L2TP tunnel service. At present only attribute 31 (Calling Station ID) can be filtered.
The Calling Station ID is filtered only from connection authentication for proxy and L2TP tunnel services and for connection accounting records sent to the remote AAA server.
Table 3 shows the format of the Service-Info VSA needed to enable attribute filtering.
Table 4 lists the attributes used for service logon with and without the MSISDN and with MSISDN filter set to F31.
Table 4 Service Logon Comparison (With MSISDN, Without MSISDN, and With MSISDN Filter)
Service Logon Connection Authentication1 Connection Accounting to Local AAA Connection Accounting to Remote AAA2 Prepaid (Re)authorization Prepaid AccountingWithout MSISDN
Host Calling ID
Host Calling ID
Host Calling ID
Host Calling ID
Host Calling ID
With MSISDN3
Connection Calling ID
Host Calling ID
Connection Calling ID
Host Calling ID
Host Calling ID
With MSISDN filter set to F31
Calling ID not sent
Host Calling ID
Calling ID not sent
Host Calling ID
Host Calling ID
1 Calling Station ID in RADIUS (attribute 31) in authentication for proxy services or calling number AVP (22) for L2TP tunnel services.
2 Only for proxy services.
3 Service profile is not set to filter MSISDN.
The show ssg connection command can be used to display the attributes that are being filtered.
Network-Address-Translated IP in Service Logon Response
External SSG clients sometimes require the real IP address of a connection on which Network Address Translation (NAT) has occurred. To provide this capability, this enhancement allows SSG to send the real IP address of translated connections in the service logon response to the SESM. The real IP address is obtained from the Access Response message for service authentication from the remote AAA server for proxy services or is assigned by the LNS for tunnel services. The real IP address is sent in an SSG Account-Info VSA.
This feature is available for both translated proxy connections and L2TP tunnel service connections.
The real IP address is also returned in response to service status queries for translated connections in an SSG Account-Info VSA.
SSG Error Codes in Access Responses
SSG provides the account logoff command to force the deletion of a host. The host is identified by the subscriber IP address (or the port-bundle when the port-map feature is enabled).
This enhancement provides the result of the account logoff in the response. If the host exists, an Access-Accept is sent. If the host does not exist, the SSG sends an Access Reject message with the error code 2.
SSG also supports the service logoff command for SESM for a connection where the host is indicated by the host IP address (or port-bundle when the port-map feature is enabled) and the service is indicated by the service name. If the connection exists, an Access Accept message is sent. If the host is not connected to the service, an Access Reject message returns with the error code 56.
Table 5 lists the attributes for the SSG error codes sent to the SESM.
For more information on RADIUS SSG VSAs, refer to "Vendor Specific Attributes" document at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cnsar/3_0/concepts/vsa.htm
Additional References
The following sections provide references related to the SSG Enhancements to SSG-SESM Interactions and Service Logon.
Related Documents
Related Topic Document TitleSSG commands
Cisco IOS Wide-Area Networking Command Reference, Release 12.3 T
SSG configuration tasks
"Broadband Access" section in the Cisco IOS Wide-Area Networking Configuration Guide, Release 12.3
SSG Features in Cisco IOS Release 12.3(4)T
SESM
Cisco Subscriber Edge Services Manager
RADIUS commands
Cisco IOS Security Command Reference, Release 12.3 T
RADIUS configuration tasks
Cisco IOS Security Configuration Guide, Release 12.3
MIBs
Technical Assistance
Command Reference
This section documents new and modified commands.
show ssg connection
To display the connections of a given Service Selection Gateway (SSG) host and a service name, use the show ssg connection command in privileged EXEC mode.
show ssg connection ip-address service-name [interface]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
Prepaid Service Based on Volume: Example
The following example displays the SSG connection for a prepaid service that uses a volume-based quota:
Router# show ssg connection 19.1.1.19 InstMsg------------------------ConnectionObject Content -----------------------User Name:Owner Host:19.1.1.19Associated Service:InstMsgConnection State:0 (UP)Connection Started since:*00:25:58.000 UTC Tue Oct 23 2001User last activity at:*00:25:59.000 UTC Tue Oct 23 2001Connection Traffic Statistics:Input Bytes = 0, Input packets = 0Output Bytes = 0, Output packets = 0Quota Type = 'VOLUME', Quota Value = 100Session policing disabledPrepaid Service Based on Time: Example
The following example displays the SSG connection for a prepaid service that uses a time-based quota:
Router# show ssg connection 19.1.1.22 Prepaid-internet------------------------ConnectionObject Content -----------------------User Name:HostOwner Host:19.1.1.22Associated Service:Prepaid-internetConnection State:0 (UP)Connection Started since:*00:34:06.000 UTC Tue Oct 23 2001User last activity at:*00:34:07.000 UTC Tue Oct 23 2001Connection Traffic Statistics:Input Bytes = 0, Input packets = 0Output Bytes = 0, Output packets = 0Quota Type = 'TIME', Quota Value = 100Session policing disabledAutologin Service: Example
The following example shows the service connection for the autologon service to host 10.3.6.1:
Router# show ssg connection 10.3.6.1 autologin------------------------ ConnectionObject Content -----------------------User Name:autologinOwner Host:10.3.6.1Associated Service:autologinConnection State:0 (UP)Connection Started since:*20:41:26.000 UTC Fri Jul 27 2001User last activity at:*20:41:26.000 UTC Fri Jul 27 2001Connection Traffic Statistics:Input Bytes = 0 (HI = 0), Input packets = 0Output Bytes = 0 (HI = 0), Output packets = 0MSISDN: Example
The following sample output for the show ssg connection command shows the MSISDN that is used for service logon:
Router# show ssg connection 10.0.1.1 proxy2------------------------ConnectionObject Content -----------------------User Name: dev-user2Owner Host: 10.0.1.1Associated Service: proxy2Calling station id: 12345Connection State: 0 (UP)Connection Started since: *17:44:59.000 GMT Sun Jul 6 2003User last activity at: *17:44:59.000 GMT Sun Jul 6 2003Connection Traffic Statistics:Input Bytes = 0, Input packets = 0Output Bytes = 0, Output packets = 0Session policing disabledTable 6 describes the significant fields shown in the displays.
Related Commands
Command Descriptionclear ssg connection
Removes the connections of a given host and a service name.
show ssg service
To display the information for a Service Selection Gateway (SSG) service, use the show ssg service command in privileged EXEC mode.
show ssg service [service-name [begin expression | exclude expression | include expression]]
Syntax Description
Defaults
If no service name is provided, the command displays information for all services.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display connection information for a service.
Examples
L2TP Tunnel Service: Example
The following example shows the information for the L2TP tunnel service called "tunnel1". The attribute filter that is set in the service profile can be seen in the output.
Router# show ssg service tunnel1------------------------ ServiceInfo Content -----------------------Uplink IDB: gw: 0.0.0.0Name: tunnel1Type: TUNNELMode: CONCURRENTService Session Timeout: 0 secondsService Idle Timeout: 0 secondsService refresh timeleft: 99 minutesNo Authorization RequiredAuthentication Type: CHAPAttribute Filter: 31Session policing disabledReference Count: 1DNS Server(s):No Radius server group created. No remote Radius servers.TunnelId: ssg1TunnelPassword: ciscoHomeGateway Addresses: 172.0.0.1ConnectionCount 1Full User Name not usedDomain List: Included Network Segments:0.0.0.0/0.0.0.0Active Connections:1 : RealIP=172.0.1.1, Subscriber=10.0.1.1------------------------ End of ServiceInfo Content ----------------Proxy Service: Example
The following example shows information for the proxy service called "serv1-proxy":
Router# show ssg service serv1-proxy------------------------ ServiceInfo Content -----------------------Uplink IDB:Name:serv1-proxyType:PROXYMode:CONCURRENTService Session Timeout:0 secondsService Idle Timeout:0 secondsClass Attr:NONEAuthentication Type:CHAPReference Count:1Next Hop Gateway Key:my-keyDNS Server(s):Primary:10.13.1.5Radius Server:IP=10.13.1.2, authPort=1645, acctPort=1646, secret=my-secretIncluded Network Segments:10.13.0.0/255.255.0.0Excluded Network Segments:Full User Name UsedService Defined Cookie existDomain List:service1.com;Active Connections:1 :Virtual=255.255.255.255, Subscriber=10.20.10.2------------------------ End of ServiceInfo Content ----------------Table 7 describes the significant fields shown in the display.
Related Commands
Copyright © 2003 Cisco Systems, Inc. All rights reserved.


