Table Of Contents
Configuring SSG Support for Subnet-Based Authentication
Prerequisites for SSG Support for Subnet-Based Authentication
Restrictions for SSG Support for Subnet-Based Authentication
Information About SSG Support for Subnet-Based Authentication
Identifying Subnet-Based Subscribers
Benefits of SSG Support for Subnet-Based Authentication
How to Configure SSG Support for Subnet-Based Authentication
Verifying SSG Support for Subnet-Based Authentication
Configuring SSG Support for Subnet-Based Authentication
The SSG Support for Subnet-Based Authentication feature allows a service provider to identify subscribers to services by their subnet, rather than by a subscriber's IP address. This module describes how the Cisco Service Selection Gateway (SSG) recognizes and manages subnet-based subscribers.
History for the Configuring SSG Support for Subnet-Based Authentication Feature
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 SSG Support for Subnet-Based Authentication
•
Restrictions for SSG Support for Subnet-Based Authentication
•
Information About SSG Support for Subnet-Based Authentication
•
How to Configure SSG Support for Subnet-Based Authentication
Prerequisites for SSG Support for Subnet-Based Authentication
SSG must be enabled before subnet-based authentication for SSG can be configured.
Restrictions for SSG Support for Subnet-Based Authentication
•
If the Port-Bundle Host Key (PBHK) feature is used with subscribers, the port bundle allocated to a subscriber will be shared for all IP addresses within the IP subnet.
•
RADIUS proxy deployments do not support subnet-based subscribers.
•
Subnet-based authentication is not supported for users with PPP-based access.
•
Once a subscriber is identified as a subnet-based subscriber, all other individual subscribers on the same subnet will be tracked as part of the same subnet subscriber.
•
Services that require Network Address Translation (NAT) are not supported.
Information About SSG Support for Subnet-Based Authentication
To configure the SSG Support for Subnet-Based Authentication feature, you should understand the following concepts:
•
Identifying Subnet-Based Subscribers
•
Benefits of SSG Support for Subnet-Based Authentication
Identifying Subnet-Based Subscribers
Subnet-based subscribers are identified whenever SSG receives a subnet mask along with an IP address from the authentication, authorization, and accounting (AAA) server. The IP address is found in the RADIUS Framed-IP (FIP) attribute (RADIUS attribute 8), and the IP subnet mask is found in the RADIUS-Framed-IP-Netmask (FIN) attribute (RADIUS attribute 9).
Benefits of SSG Support for Subnet-Based Authentication
Subnet-based authentication of subscribers gives service providers the option to provide services to their enterprise customers based on the IP subnet rather than on an individual IP address. This capability eliminates the need for each subscriber to self-identify and log in. Applications of subnet-based authentication include business internet services, video streaming, and pay-per-use Internet access for small office/home office (SOHO) customers.
How to Configure SSG Support for Subnet-Based Authentication
No configuration is required to identify subnet-based subscribers. Whenever SSG receives a subscriber's IP address and subnet mask from the AAA (RADIUS) server, SSG will treat that subscriber as a subnet-based subscriber.
This section contains the following task:
•
Verifying SSG Support for Subnet-Based Authentication (optional)
Verifying SSG Support for Subnet-Based Authentication
This optional task explains how to verify subnet-based authentication for SSG. The commands contained in the task steps can be used in any sequence and may need to be repeated.
SUMMARY STEPS
1.
enable
2.
show ssg connection {ip-address | network-id subnet-mask} service-name [interface]
3.
show ssg host [ip-address | count | username] [interface [username] [subnet-mask]]
DETAILED STEPS
Step 1
enable
Enables privileged EXEC mode. Enter your password if prompted.
Router> enableStep 2
show ssg connection {ip-address | network-id subnet-mask} service-name [interface]
Displays the connections of a given SSG host and service name. To display the connections of the specified subnet-based subscribed host, enter the network ID and IP subnet mask.
Router# show ssg connection 10.0.1.1 255.255.255.0 passthru------------------------ConnectionObject Content -----------------------User Name: dev-user2Owner Host: 10.0.1.1 (Mask : 255.255.255.0)Associated Service: passthru1Calling station id: 00d0.792f.8054Connection State: 0 (UP)Connection Started since: *17:44:59.000 GMT Sun Jul 6 2004User last activity at: *17:44:59.000 GMT Sun Jul 6 2004Connection Traffic Statistics:Input Bytes = 0, Input packets = 0Output Bytes = 0, Output packets = 0Step 3
show ssg host [ip-address | count | username] [interface [username] [subnet-mask]]
Displays information about a subscriber and the subscriber's current connections. To display information about the specified subnet-based subscribed host, enter the IP subnet mask.
Router# show ssg host 10.0.0.0 255.255.255.0------------------------ HostObject Content -----------------------Activated: TRUEInterface:User Name: user1Host IP : 10.0.0.0Mask : 255.255.255.0Msg IP: 0.0.0.0 (0)Host DNS IP: 0.0.0.0Maximum Session Timeout: 0 secondsHost Idle Timeout: 60000 secondsClass Attr: NONEUser policing disabledUser logged on since: *05:59:46.000 UTC Fri May 3 2004User last activity at: *05:59:52.000 UTC Fri May 3 2004SMTP Forwarding: NOInitial TCP captivate: NOTCP Advertisement captivate: NODefault Service: NONEDNS Default Service: NONEActive Services: NONEAutoService: NONESubscribed Services: passthru1; proxynat1; tunnel1; proxy1Subscribed Service Groups: NONE
Additional References
The following sections provide references related to the SSG Support for Subnet-Based Authentication feature.
Related Documents
Standards
Standards TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFCs 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.
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 | network-id subnet-mask} 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 10.10.1.1 InstMsg------------------------ConnectionObject Content -----------------------User Name:Owner Host:10.10.1.1Associated 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 10.10.1.2 Prepaid-internet------------------------ConnectionObject Content -----------------------User Name:HostOwner Host:10.10.1.2Associated 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 disabledSubnet-Based Subscriber: Example
The following sample output for the show ssg connection command shows the subnet mask of the subscribed host:
Router# show ssg connection 10.0.1.1 255.255.255.0 passthru------------------------ConnectionObject Content -----------------------User Name: dev-user2Owner Host: 10.0.1.1 (Mask : 255.255.255.0)Associated Service: passthru1Calling station id: 00d0.792f.8054Connection State: 0 (UP)Connection Started since: *17:44:59.000 GMT Sun Jul 6 2004User last activity at: *17:44:59.000 GMT Sun Jul 6 2004Connection Traffic Statistics:Input Bytes = 0, Input packets = 0Output Bytes = 0, Output packets = 0Table 1 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 host
To display information about a Service Selection Gateway (SSG) subscriber and the current connections of the subscriber, use the show ssg host command in privileged EXEC mode. The command syntax of the show ssg host command depends on whether the SSG Port-Bundle Host Key feature is enabled.
When SSG Port-Bundle Host Key Is Not Enabled
show ssg host [ip-address | count | username [subnet-mask]]
When SSG Port-Bundle Host Key Is Enabled
show ssg host [ip-address | count | username] [interface [username] [subnet-mask]]
Syntax Description
Defaults
If no argument is provided, all current connections are displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can specify the Service Selection Gateway (SSG) downlink interface only when the SSG Port-Bundle Host Key feature is enabled. To enable the host key, enter the ssg port-map command in global configuration mode. To disable the host key, enter the no ssg port-map command.
Examples
Display All Active Hosts: Example
The following example shows all active hosts:
Router# show ssg host1:10.3.1.1 [Host-Key 70.13.60.3:64]2:10.3.6.1 [Host-Key 70.13.60.3:65]### Active HostObject Count:2Simple IP Host: Example
The following example shows information about a simple IP host with an IP address of 10.0.0.0:
Router# show ssg host 10.0.0.0------------------------ HostObject Content -----------------------Activated: TRUEInterface:User Name: user1Owner Host: 10.0.0.0Msg IP: 0.0.0.0 (0)Host DNS IP: 0.0.0.0Proxy logon from client IP: 10.0.48.3Device: PDSN (Simple IP)NASIP : 10.0.48.3SessID: 12345678APN :MSID : 5551000Timer : NoneMaximum Session Timeout: 0 secondsHost Idle Timeout: 60000 secondsClass Attr: NONEUser policing disabledUser logged on since: *05:59:46.000 UTC Fri May 3 2002User last activity at: *05:59:52.000 UTC Fri May 3 2002SMTP Forwarding: NOInitial TCP captivate: NOTCP Advertisement captivate: NODefault Service: NONEDNS Default Service: NONEActive Services: internet-blue;AutoService: internet-blue;Subscribed Services: internet-blue; iptv; games; distlearn; corporate; shop; banking; vidconf;Subscribed Service Groups: NONEMobile IP Host: Example
The following example shows information about a mobile IP host with an IP address of 10.0.0.0:
Router# show ssg host 10.0.0.0------------------------ HostObject Content -----------------------Activated: TRUEInterface:User Name: user1Owner Host: 10.0.0.0Msg IP: 0.0.0.0 (0)Host DNS IP: 0.0.0.0Proxy logon from client IP: 10.0.48.4Device: HANASIP : 10.0.48.4SessID: 44444445APN :MSID : 5551001Timer : NoneMaximum Session Timeout: 0 secondsHost Idle Timeout: 60000 secondsClass Attr: NONEUser policing disabledUser logged on since: *06:01:02.000 UTC Fri May 3 2002User last activity at: *06:01:09.000 UTC Fri May 3 2002SMTP Forwarding: NOInitial TCP captivate: NOTCP Advertisement captivate: NODefault Service: NONEDNS Default Service: NONEActive Services: internet-blue;AutoService: internet-blue;Subscribed Services: internet-blue; iptv; games; distlearn; corporate; shop; banking; vidconf;Subscribed Service Groups: NONETwo Hosts with the Same IP Address: Examples
The following example shows two host objects with the same IP address:
Router# show ssg host 10.3.1.1SSG:Overlapping hosts for IP 10.3.1.1 at interfaces:FastEthernet0/0/0Virtual-Access1In this case, use the interface argument to uniquely identify the host:
Router# show ssg host 10.3.1.1 FastEthernet0/0/0...
Note
Note that the output produced by this command is the same as that produced by the command without the interface argument. The interface argument is used to uniquely identify a host only when there are overlapping host IP addresses.
The following example shows the usernames logged in to the active hosts:
Router# show ssg host username1:10.3.1.1 (active) Host name:pppoauser2:10.3.6.1 (active) Host name:ssguser2### Total HostObject Count(including inactive hosts):2Host Associated with a VRF: Example
The following sample output for the show ssg host command shows a VRF called "BLUE" associated with a host that has the IP address 10.0.0.2:
Router# show ssg host 10.0.0.2------------------------ HostObject Content ----------------------Activated: TRUEInterface: Ethernet1/0 VRF Name: BLUEUser Name: prep-user1Owner Host: 10.0.0.2Subnet-Based Subscriber: Example
The following example shows information about a subnet-based subscriber with an IP address of 10.0.0.0 and a subnet mask of 255.255.255.0:
Router# show ssg host 10.0.0.0 255.255.255.0------------------------ HostObject Content -----------------------Activated: TRUEInterface:User Name: user1Host IP : 10.0.0.0Mask : 255.255.255.0Msg IP: 0.0.0.0 (0)Host DNS IP: 0.0.0.0Maximum Session Timeout: 0 secondsHost Idle Timeout: 60000 secondsClass Attr: NONEUser policing disabledUser logged on since: *05:59:46.000 UTC Fri May 3 2004User last activity at: *05:59:52.000 UTC Fri May 3 2004SMTP Forwarding: NOInitial TCP captivate: NOTCP Advertisement captivate: NODefault Service: NONEDNS Default Service: NONEActive Services: NONEAutoService: NONESubscribed Services: passthru1; proxynat1; tunnel1; proxy1Subscribed Service Groups: NONETable 2 describes the significant fields shown in the displays.
Related Commands
Command Descriptionclear ssg host
Removes a host object or a range of host objects.
ssg port-map
Enables the SSG port-bundle host key.
Copyright © 2005 Cisco Systems, Inc. All rights reserved.


