![]() |
Intelligent Services Gateway Configuration Guide, Cisco IOS XE Release 3S
|
||||||||||||
ISG RADIUS Proxy Support for Mobile Users: Hotspot Roaming and Accounting Start Filtering
![]() |
|||||||||||||
|
Contents
ISG RADIUS Proxy Support for Mobile Users--Hotspot Roaming and Accounting Start FilteringLast Updated: January 31, 2013
Finding Feature InformationYour software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and 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 table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Restrictions for ISG RADIUS Proxy Support for Mobile Users--Hotspot Roaming and Accounting Start Filtering
Restrictions for RADIUS Proxy Support for Hotspot RoamingA subscriber is connected to an access point (AP1) that is connected to an Access Zone Router (AZR) (AZR1). The subscriber moves to a different AZR and moves back to a different access point (AP2) within AZR1. When the subscriber tries to reauthenticate with the same IP address that it had for AP1, ISG cannot determine that it is a new session with AP2 and terminates the session when the roaming timer expires. Information About ISG RADIUS Proxy Support for Mobile Users--Hotspot Roaming and Accounting Start FilteringHotspot Roaming TimerWhen an Extensible Authentication Protocol (EAP)-authenticated subscriber moves from one hotspot to another (hotspot roaming), the subscriber authenticates against a new access point. ISG checks the following conditions to validate if the user has roamed from one hotspot to another:
If the reauthentication on hotspot roaming is successful, the ISG RADIUS proxy server saves the following data in the RADIUS proxy session context:
If the reauthentication fails, ISG clears the session.
If reauthentication is successful, ISG receives an accounting-start request on the existing session from the new access point, with a different IP address. ISG creates a new RADIUS proxy session for the subscriber with a new IP address and provides seamless roaming by applying the services saved during reauthentication if the following conditions are satisfied:
If the new session is created successfully, a roaming timer is started for the first session. Use the timer roaming command in RADIUS proxy server configuration and RADIUS proxy client configuration modes to configure the roaming timer. Once the cleanup timer expires, ISG clears the first session, and the second session remains as the only session for the subscriber. If the subscriber moves back to the first hotspot before the roaming timer expires on the first session and reauthentication is successful, the roaming timer is stopped for the first session. A new roaming timer is initiated for the second session. If the reauthentication fails, the first session is cleared. If ISG receives an accounting-stop request for the first session from the AZR to which the session belongs, before the roaming timer expires, the timer is stopped and the first session is cleared. The accounting-stop request is forwarded to the RADIUS server. The response from the RADIUS server is forwarded to the AZR. If the subscriber roams between multiple hotspots, ISG creates multiple parallel sessions. All these sessions are maintained on ISG until the roaming timer associated with them expires. Only the session that is authenticated last is not associated with a roaming timer. RADIUS Packet Filter CreationThe RADIUS filter consists of a filter structure and a CLI through which subscribers can configure the filter on RADIUS packets. When a packet is received by ISG, ISG reads the attributes in the packet and matches them with the attributes defined in the filter. Depending on the match criteria that are specified in the filter, ISG takes the defined action on the RADIUS packet. To create a RADIUS packet filter, follow three steps: How to Configure ISG RADIUS Proxy Support for Mobile Users--Hotspot Roaming and Accounting Start Filtering
Configuring a Roaming Timer for the ISG RADIUS Proxy SessionSUMMARY STEPS
DETAILED STEPS Configuring RADIUS Proxy Support for Accounting Start FilteringThe Accounting Start Filtering feature allows the creation of RADIUS packet filtering to filter packets that reach ISG. Based on the defined filter criteria, ISG performs certain actions on the RADIUS packet. The RADIUS packet filter is created on ISG by defining the filter name and the match criteria in the radius filter command. The match criteria are applied to the attributes of the RADIUS packet. When you configure the radius filter match-all command, the filter is applied to the RADIUS packet only if all the attributes configured in the command match the attributes in the RADIUS packet. When you configure the radius filter match-any command, the filter is applied to the RADIUS packet if at least one attribute configured in the command matches the attributes in the RADIUS packet. The attributes to match are defined in RADIUS filter configuration mode. In RADIUS filter configuration mode, you can specify a standard IETF RADIUS attribute or a vendor-specific RADIUS attribute. These attributes must match the attributes in the RADIUS packet so that the filter can be applied accordingly. The match command checks if the attribute is present in the packet, and the matchnot command checks if the attribute is not present in the packet. Apply RADIUS filters to the RADIUS proxy server in order for the configuration to take effect. Apply RADIUS filters in RADIUS proxy server configuration mode and RADIUS proxy client configuration mode. If filters are applied in both modes, only the client mode configuration will take effect. You can specify the type of RADIUS packets to which the filter should be applied using the filter access and filter accounting commands. You can configure any one of the following three actions that the RADIUS proxy server should apply to the incoming RADIUS packets to complete the filtering process:
Perform the following tasks to configure a RADIUS packet filter and apply the filter criteria to RADIUS proxy. Configuring a RADIUS Packet FilterSUMMARY STEPS
DETAILED STEPS Applying RADIUS Filters to RADIUS Proxy Server or ClientUse the filter command in RADIUS proxy server configuration mode or RADIUS proxy client configuration mode to apply a RADIUS filter. If the RADIUS filter is configured in both these modes, only the filter configured in the client mode will be applied. DETAILED STEPS Configuration Examples for ISG RADIUS Proxy Support for Mobile Users--Hotspot Roaming and Accounting Start Filtering
Example: Configuring a RADIUS Packet FilterUse the following example along with the example given in the "Example: Applying RADIUS Packet Filters to RADIUS Proxy Mode" section to configure a RADIUS packet filter for the RADIUS proxy server. The following example shows how to create the RADIUS packet filter, filter1, and define the matching conditions: Device> enable Device# configure terminal Device(config)# radius filter match-all filter1 Device(config)# match attribute 25 Device(config)# match attribute 100 Device(config)# matchnot vendor-type 100 Example: Applying RADIUS Packet Filters to RADIUS Proxy ServerUse the following example along with the example given in "Example: Configuring a RADIUS Packet Filter" section to configure a RADIUS packet filter for the RADIUS proxy server. Device> enable Device# configure terminal Device(config)# aaa new-model Device(config)# aaa server radius proxy Device(config-locsvr-proxy-radius)# filter access ack filter1 Additional ReferencesTechnical Assistance
Feature Information for ISG RADIUS Proxy Support for Mobile Users: Hotspot Roaming and Accounting Start FilteringThe following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R) 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. © 2013 Cisco Systems, Inc. All rights reserved.
|
||||||||||||
|
|